[chore] Update spec version using renovate

[thompson-tomo]

Changes

This replaces the shell script and workflow which mantains spec version with a renovate manager

Important

Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions)

[trask]

@thompson-tomo have you tested it on your fork? just know from experience it's hard (for me) to get these custom rules right, thanks

[thompson-tomo]

@trask you are right it is hard to test them end to end. What I have been able to test using the renovate cli is:

• are the references (dependencies) being detected
• is it finding updates when it should be including resolving to the right version. To do so I tested using a commit prior to the recent changes
• when the docs have been updated do the needed updates decrease.

What I have not tested is what the contents of a pr looks like when raised by renovate.

[github-actions]

This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days.

[github-actions]

This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days.

[github-actions]

This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days.