Release prep for 0.4.4

[erikbosch]

Background/Rationale:

• Previous release of databroker in old kuksa.val repo was 0.4.1
• But we have used 0.4.2 for kuksa-client in kuksa.val
• And we intend to release 0.4.3 with deprecation warning from old repo, see Add deprecation/migration note to Databroker eclipse/kuksa.val#762

0.4.4 is intended to be essentially equal with 0.4.1

I opted for updating "all versions", i.e. not keeping "0.1.0" for "unreleased" packages, but if we want to keep "0.1.0" that works too

[SebastianSchildt]

Which reminds me, we need t get better updating the cargo lock versions, becasue "tag-wise" there WAS a 0.4.2 release fo databroker as well (it has basically all additons over 0.4.1 making int RISCV compatible. seems we just forgot to changee cargo file. Therefore, my suggestion would be, after merging this and then tagging an actual relase, in main we should immediately bump all cargo versions

[SebastianSchildt]

Looking good. I quickly started databroker and databroker-cli containers. Seems to work, but did not do full testing with providers etc,

[erikbosch]

Which reminds me, we need t get better updating the cargo lock versions, becasue "tag-wise" there WAS a 0.4.2 release fo databroker as well (it has basically all additons over 0.4.1 making int RISCV compatible. seems we just forgot to changee cargo file. Therefore, my suggestion would be, after merging this and then tagging an actual relase, in main we should immediately bump all cargo versions

In this PR I update Cargo.lock, so when merged Cargo.lock in main will be updated.
I did not know or did not remember that we triggered a docker build of 0.4.2 (possibly as you triggered the build :-))