[do-not-merge]: tracking diff

[Gigas002]

Tracking from testing branch what's done and what's yet to do. After some usage when I'm sure everything works as expected will propose changes to main repo

1. [PR] freeze option
2. [PR] deps upgrades merged
3. (soft dep on 1) delay option
4. (soft dep on 3) geometry slurp
5. (5 or 6 first, next dep) vulkan module
6. (5 or 6 first, next dep) egl module + very light refactor (due to moving stuff)
7. (soft dep on 6) refactor libwayshot tests
8. (preferrrably after 7) revert 290 (or at least find a way to fix it ffs)
9. (soft dep on 7) add benches
10. [PR] refactor ci
11. [PR] cargo deny + licensing issues

[Gigas002]

TODO:

• Consider adding CONTRIBUTING.md with guidelines for new contributors on simple things how to add stuff and why already have one
• wayshot cli tests
• is libwayshot's examples for excluded? It should be but better check, in worst case add feature
• Ci --all-features tests? Probably not possible (especially for vk) but worth taking a look
• Bench reports in pr response (probably requires some 3rd party bot, so not much hope here) looks too complicated for nothing really useful
• Node 20 deprecation notice (codecov issue: Node.js 20 deprecation warning caused by actions/github-script dependency codecov/codecov-action#1919)