Use Semver type in version info response

[timvisee]

schemars supports the semver type. Since we expose a semver I decided to explore the idea of using the respective type there.

As shown in the OpenAPI specification this constrains the allowed pattern to match the semver specification. Though not necessary, I think that's a valid addition.

Any objections or thoughts?

All Submissions:

• Contributions should target the dev branch. Did you create your branch from dev?
• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests?
2. Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
3. Have you checked your code using cargo clippy --all --all-features command?

[agourlay]

Fine for me if the Python REST client is fine :)

[timvisee]

Fine for me if the Python REST client is fine :)

Yeah, I'll give checking that a shot.

[timvisee]

Fine for me if the Python REST client is fine :)

Generating the REST client and running integration tests works fine 👍

[generall]

Any objections or thoughts?

no objections, but what problem does it solve?

[timvisee]

no objections, but what problem does it solve?

None.

It just adds more type information. Since that is supported out of the box I figured; why not.

[timvisee]

Closing this since I don't think we're enthusiastic enough about this change 😄