Upstream issues

[arcnmx]

Here's a dumping ground for various problems and limitations that I've run into while working with the wp api. Need to clean up and report some of these maybe.

• [ ] wp_spa_pod_parser_new_object gives you a string instead of the much more useful numeric ID, I can do my own id table lookups thanks :disappointed:
• [ ] no apparent way to get property flags despite the wp_spa_pod_get_property docs implying otherwise?
• [ ] no apparent way to get flags or know if a WpSpaPod is const or not
• [ ] WpObjectInterest has no accessor for self.gtype
• [ ] the gir xml contains a bunch of inaccurate information
• [ ] please rethink using lua-style GVariants as a poor man's ABI - why should a module be required to decode a goddamn <{"1": <whatever>}> a{sv} variant as an array, what is wrong with you why is this such a lua-centric worldview... there is no reason why all plugins must be subjected to lua's idiosyncrasies :<
• [ ] pipewire-rs requiring bindgen at build time has been a longstanding issue that prevents us from publishing to docs.rs and introduces a bunch of hacks into the build and cfgs
• [ ] cargo package --list --allow-dirty -p wireplumber-sys omits critical files if sys/generate/Cargo.toml exists, despite gitignore and an explicit include = ["generate/etc"] maybe report this as a cargo bug? it presumably believes that sys/generate is a sub-crate and ignores its files