fix(opentofu): use semver versionFilter instead of latest

[Copilot]

kind: latest picks the most recently published GitHub release, which can be out of semver order (e.g. a backported patch on an older minor published after a newer release). Switching to kind: semver ensures the policy always resolves the highest semantic version.

Changes

-      versionFilter:
-        kind: latest
+      versionFilter:
+        kind: semver

• Policy.yaml: bumped policy version from 0.1.0 to 0.2.0 (minor release)
• CHANGELOG.md: added 0.2.0 entry documenting the semver filter change
• CONTRIBUTING.md: added guidance clarifying that new features, bug fixes, and enhancements require updating both Policy.yaml (with semver bump guidance) and CHANGELOG.md

Ref: https://www.updatecli.io/docs/plugins/resource/github_release/

Original prompt

---

This section details on the original issue you should resolve

<issue_title>opentofu policies picks up the latest available releases without any semver order</issue_title>
<issue_description>Let's use the semver filter without any patterns instead of the latest kind as explained at https://www.updatecli.io/docs/plugins/resource/github_release/

Policy file: https://github.com/elastic/oblt-updatecli-policies/blob/main/updatecli/policies/opentofu/version/updatecli.d/default.tpl

Type of change: minor change

Further details:

• https://github.com/elastic/oblt-updatecli-policies/blob/main/CONTRIBUTING.md

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes opentofu policies picks up the latest available releases without any semver order #202

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[v1v]

@copilot, if a new change it requires to release the policy for such, it requires a few changes:

• Policy.yaml
• CHANGELOG.md

Update them as a minor update.

Also update the existing documentation in the contributions.md to help with explaining that new features/ bug fixes, enhancements require updating those files accordingly

[Copilot]

@copilot, if a new change it requires to release the policy for such, it requires a few changes:

• Policy.yaml
• CHANGELOG.md
  ...

Done in commit 65706e0:

• Policy.yaml bumped to 0.2.0
• CHANGELOG.md updated with a 0.2.0 entry describing the semver filter change
• CONTRIBUTING.md updated with explicit guidance that new features, bug fixes, and enhancements require bumping the Policy.yaml version (with semver guidance) and adding a CHANGELOG.md entry

[v1v]

Tests

[fr4nc1sc0-r4m0n]

LGTM