fix(DF-922): remove legacy version metadata fallback from adapter for…

[mokhld]

…matter

Proposed change

Remove getVersionMetadata and the formMetadata.versions fallback path that was producing fabricated versionNumber values for pre-versioning forms. Version metadata now resolves solely from $$__formVersion embedded in the form definition by the manager.

Also removes the now-dead submittedVersionNumber from FormContext and versionNumber from `FormModel, which only existed to feed the deleted fallback.

Jira ticket: https://eaflood.atlassian.net/browse/DF-972?atlOrigin=eyJpIjoiYTA1N2NhNjFlZWE1NDA0NDg0YzNhNjdkNTIzMzViOWEiLCJwIjoiaiJ9

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