2024.6 Bitwarden uses camelCase keys instead of PascalCase

[OdyX]

This fixes client access to a 1.31 Vaultwarden instance, see:

• https://github.com/dani-garcia/vaultwarden/releases/tag/1.31.0
• "Change API and structs to camelCase by @dani-garcia" in Change API and structs to camelCase dani-garcia/vaultwarden#4386

[commonism]

Required for Vaultwarden 1.31 released 08.07.2024

https://github.com/dani-garcia/vaultwarden/releases/tag/1.31.0

Change API and structs to camelCase by @dani-garcia in dani-garcia/vaultwarden#4386

[commonism]

@kiorky - this needs your attention, all tooling using bitwarden tools is broken by the API changes and require these updates.

[kiorky]

As it is , i do not know what to do because this PR seems highly backward incompatible, and do not know if i have currently enough bandwidth to do more than a review ...

If someone can contribute some glue to try/fallback on new (non camelcase) vs old structure, i will be happy to merge it.

[commonism]

Would you accept a patch which makes use of pydantic to process/validate the json?
pydantic is quite a dependency but … besides best in class validation it adds comfort.

e.g. - https://docs.pydantic.dev/latest/concepts/alias/

[kiorky]

Hello, i want to thanks you very much as it largely inspired the latest release with my own fix !