Add the golden rules of performance-oriented Haskell

[doyougnu]

One of them must be:

• dont miss the data cache

be sure to update the memory footprint chapter #61 #16

[doyougnu]

• you will always know more about your system than the compiler does

or in other words

• the compiler will not save you

or in other other words

• the performance (or lack thereof) of your system is up to you

[doyougnu]

perhaps integrate these blogs as well:

• https://tratt.net/laurie/blog/2023/four_kinds_of_optimisation.html
• https://tratt.net/laurie/blog/2025/the_fifth_kind_of_optimisation.html

They define "kinds" of optimizations, but they are all really ways of creating less pessimized code. The good points are not technical but architectural. Advice such as "perhaps trade off correctness for performance" is great advice and the book should discuss this.