Implement proper support for `id_v1` and v1 api

[chrivers]

So far, bifrost only supported barely enough of the v1 api to find a bridge, which is needed by the hue app.

Other apps, like Hue Essentials, still depend heavily on the v1 api, and did not work with bifrost.

One issue is that bifrost tried to use UUIDs for id_v1, which is (maybe?) valid according to the spec, but many clients expect a decimal number (in string form).

So we build an internal id_v1 index tracker, to generate these ids as needed, and implement the necessary endpoints to interact with lights, rooms and scenes.

This brings Hue Essentials mostly up to par with the Hue App.

• Flesh out implementation-status.md after implementing more v1 support
• Refactor v1 hue structs to use references instead of ownership. This simplifies code, and saves on cloning
• Rename V1ReplyBuilder to V1Reply, and use helper functions to simplify put_api_user_resource_id()
• Fix logging for get_api_user_resource_id()
• Drop lock early (clippy lint)
• Add helper functions on V1ReplyBuilder
• Add handling of scene recall for api v1
• Improve request debugging for put_api_user_resource_id()
• Add legacy api models needed for scene recall
• Add POST handler for api v1, which dumps request and returns ApiError::V1CreateUnsupported
• Add ParseIntError to error mapping
• Fail early in put_api_user_resource_id() to reduce indentation
• Support .appdata for ApiScene. This makes scenes show in Hue Essentials!
• Move IntoResponse impl for ApiError into src/routes/mod.rs
• Simplified code by letting get_id_v1() return Option
• Fixed variable naming
• Implement proper id_v1 mapping for v1 api results
• Merge branches of api error mapping (clippy lint)
• Implement better support for id_v1
• Add http status code mapping for V1CreateUnsupported and V1NotFound
• Add get_id_v1() / from_id_v1() to Resources
• Add from_id_v1() to State, and add missing #[must_use]
• Add get() and try_get() to State
• Add V1NotFound variant to Error
• Reduce verbosity of h2 log messages
• Added partial support for id_v1 links event stream updates
• Added .id_v1() and .insert() to struct State, and use IdMap for id_v1 mapping
• Implemented struct IdMap for tracking forwards/backwards lookups between Uuid and id_v1
• Refactor Resources to use State struct, and move AuxData to state.rs too
• Add new struct model::state::State for managing the bridge resources
• Move state.rs into server/appstate.rs

[chrivers]

Fixed the last issue I had with this branch: State file upgrading.

The state file (state.yaml, unless specified otherwise in the config) has had two unnamed fields in previous versions of bifrost.

Now, it gains a version field, and it is automatically upgraded when a newer bifrost release runs. A backup of the old state file is saved, in case the user wants to go back to the previous bifrost.