scmi: Prepare v0.2.0 release

[slp]

Update CHANGELOG.md and Cargo.toml for v0.2.0 relase.

[slp]

CI failure doesn't seem to be related to this PR:

test audio_backends::pipewire::tests::test_pipewire_backend_invalid_stream ... FAILED
--
  |  
  | failures:
  |  
  | ---- audio_backends::pipewire::tests::test_pipewire_backend_invalid_stream stdout ----
  | INFO: dbus_session_bus_address=unix:path=/tmp/.tmpG1gbPk/dbus
  | INFO: Wait for dbus to setup...
  | INFO: Launch pipewire.
  | INFO: Wait for pipewire to setup...
  | thread 'audio_backends::pipewire::tests::test_pipewire_backend_invalid_stream' panicked at vhost-device-sound/src/audio_backends/pipewire.rs:97:42:
  | Failed to connect to core: CreationFailed
  | INFO: Killing pipewire pid 4538
  | ERROR: pipewire stderr [E][07173.540058] mod.rt       \| [     module-rt.c:  236 pw_rtkit_bus_get()] Failed to connect to system bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
  | [W][07173.540068] mod.rt       \| [     module-rt.c: 1055 pipewire__module_init()] Realtime scheduling disabled: unsufficient realtime privileges, Portal not found on session bus, and no system bus for RTKit: Connection refused
  | [W][07173.543531] default      \| [        thread.c:  101 impl_acquire_rt()] acquire_rt thread:0x759284bcb640 prio:-1 not implemented

Seems like that pipewire test depends on a running system-wide dbus. Is that expected to work in a buildkite container?

[epilys]

@slp IIRC this is a transient failure, it only fails sometimes. We'd need to re-run the CI.

[stefano-garzarella]

@slp IIRC this is a transient failure, it only fails sometimes. We'd need to re-run the CI.

yep, just restarted and everything is fine.

[stefano-garzarella]

I'll tag it and release in a couple of minutes