feat(DF-922): read form version from definition metadata

[mokhld]

Proposed change

Reads $$__formVersion from the form definition metadata, injected by forms-manager, instead of metadata.versions for version tracking and falls back to metadata.versions in the adapter output for backward compatibility, until this is stable in prod then we can look to remove it.

Jira ticket:

Type of change

• Bug fix
• New feature
• Breaking change
• Misc. (documentation, build updates, etc)

Checklist

• You have executed this code locally and it performs as expected.
• You have added tests to verify your code works.
• You have added code comments and JSDoc, where appropriate.
• There is no commented-out code.
• You have added developer docs in README.md and docs/* (where appropriate, e.g. new features).
• The tests are passing (npm run test).
• The linting checks are passing (npm run lint).
• The code has been formatted (npm run format).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jbarnsley10]

Should the call to getFormVersion handle the fallback to old metadata, so it's all in one place?

[jbarnsley10]

Looks good. Just the one comment about the fallback being in the one getFormVersion method. I'll leave that up to you to decide. Approved anyway

[mokhld]

Looks good. Just the one comment about the fallback being in the one getFormVersion method. I'll leave that up to you to decide. Approved anyway

getFormVersion reads from the definition only. The adapter's fallback to metadata.versions is intentionally separate and temporary and would be removed in the follow up ticket.. good spot though.