Feat/update libs

[pum-purum-pum-pum]

This PR updates the crates and fixing clippy warnings.
The part with the

pub use gen::manager::ManagerServicesChanged;
pub use gen::service::ServicePropertyChanged;
pub use gen::technology::TechnologyPropertyChanged;

is mainly a way to implement property updates on my side. But I'm not sure what API would be nice to expose it. Maybe it's ok if we expose the generated types? Maybe as gen module?

[jmagnuson]

Sorry, I totally missed this.

I tried experimenting with signals in feature/signals a while (wow, 4 years) ago, but it felt pretty unwieldy and I got busy with other things. Do you have an example of how to use something like ServicePropertyChanged?

As an aside, I have started writing supplicant-rs using zbus rather than dbus-rs, just to see how it compares. Similar features may exist in dbus-rs by now, but the code generation in zbus makes working with signals pretty easy. For example, interface_state_stream.rs essentially gives asynchronous state updates for the wlan0 interface.

[pum-purum-pum-pum]

Yeah thanks!
I'll have a look at your branch at some point (shifted focus from WiFi right now)
Sure! I don't have any design for signals, the way I used it is like that I just manually add a match to connection:

        let service_property_mr = ServicePropertyChanged::match_rule(None, None);
        let _properties_changed_signal = runtime.block_on(async {
            Ok(connection
                .add_match(service_property_mr)
                .await
                .map_err(WifiManagerStartError::FailedToAddMatchToConnection)?
                .cb(move |message, property_change: ServicePropertyChanged| {
....

Basically this monitors whenever we receive the signal and calls this callback (In "..." in my particular case I send it through the channel to some other place which needs to handle this signal)