Added range limits to measurements which can be physically limited.

[peci1]

🎉 New feature

Summary

I've added min/max range and resolution to measurements where it makes sense. In some cases, the <range> tags were already there, so I've only replaced them by the refactored-out one.

This is only a proof of concept, adding the tags to SDF files only. Once there is agreement where these tags make sense, I can proceed adding them to the implementation files.

What it the general rule for adding new tags to existing SDF spec (1.12 here)? Can it be done? Or should there be a "rolling" version of SDF where new features are added until a release is made?

Test it

No testing possible at this moment.

Checklist

• Signed all commits for DCO
• Added a screen capture or video to the PR description that demonstrates the feature
• Added tests
• Added example and/or tutorial
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• Updated Bazel files (if adding new files). Created an issue otherwise.
• While waiting for a review on your PR, please help review another open pull request to support the maintainers
• Was GenAI used to generate this PR? If so, make sure to add "Generated-by" to your commits. (See this policy for more info.)

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by and Generated-by messages.

Backports: If this is a backport, please use Rebase and Merge instead.