Addon docs should use versioned branch when available

[jsetton]

The problem

Currently, the addon documentation is being retrieved from either the final (dev) or final-stable (release) branch of the openhab-docs GitHub project. When a new version is released, the final-stable branch is copied into a new versioned branch (e.g. final-4.2.x) while the final is copied into final-stable as the latest release.

This means that older releases are pointing to the final-stable branch and therefore including all the changes to the documentation from all the new releases that came after.

Expected behavior

For release version, the addon documentation should be retrieved from the versioned branch first, if available, based on the runtime version, otherwise fallback to the final-stable branch. This will prevent older releases from showing changes that aren't part of them.

Steps to reproduce

Using OH 4.2, check the Insteon addon description details. The documentation for OH 4.3 release is displayed.

[jimtng]

It would be much easier to do this if the docs uses final-4.3.x instead of final-stable.

[jsetton]

Perhaps that's a discussion that should happen in openhab-docs? How would it be backward compatible?

[jimtng]

How would it be backward compatible?

good question. Older versions will still try to look in final-stable!