wayland: Move hash algorithm to foldhash

[notgull]

A few years ago, I asked if we should use a different hash algorithm for our hash maps in the Wayland backend. We decided on using ahash, given that
it was the default in hashbrown at the time.
However, hashbrown has since moved to foldhash, along with the rest of the Rust community. So this PR moves this crate to foldhash as well.

This move is done for two primary reasons:

• This reduces the number of dependencies in the tree for most GUI
  projects. As other projects use foldhash now, this removes ahash
  (as well as its five dependencies) from the tree.

• In most cases, foldhash is faster than ahash.

• Tested on all platforms changed

• Added an entry to the changelog module if knowledge of this change could be valuable to users

• Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior

• Created or updated an example program if it would help users understand this functionality

[notgull]

cc @kchibisov, I know this is performance-sensitive for alacritty.

[notgull]

Hmm, looks like CI is failing because foldhash is released under the Zlib license. Given that a significant portion of our software in this tree is also released under Zlib (e.g. bytemuck), I doubt this should be an issue. That being said, I'm no longer a maintainer, so I'll only add it to the file if given the go-ahead.

[notgull]

TODO: See if there's a way to resolve this from the wayland-rs end

[kchibisov]

cc @kchibisov, I know this is performance-sensitive for alacritty.

winit code is not perf sensitive to alacritty, but we do use ahash in alacritty and it demonstrated to be faster than other algs.

[notgull]

Was foldhash included in those tests?

[kchibisov]

I think not, I'll retest, but winit can use anything pretty much.