doc: update version pattern <cli version>-<year>.<month>

[erisu]

Motivation and Context

Support new versioning pattern for docs.

Description

Updated tooling that updates current released docs and creating new snapshots to support current and new version pattern.

New pattern: <cli version>-<year{4}>.<month{2}>

Example: 12.x-2024.10

Testing

npx gulp newversion

• Creates new snapshot
• Updates VERSION file with new current version
• with --bumpCli flag
  • Confirm new snapshot to contain directory with new pattern 13.x-2024.10
  • Confirm new snapshot to create new toc file with new pattern en_13-x-2024-10-src.yml
• without --bumpCli flag
  • Confirm new snapshot to contain directory with new pattern 12.x-2024.10
  • Confirm new snapshot to create new toc file with new pattern en_12-x-2024-10-src.yml
• without --bumpCli flag and snapshot already existed
  • Errors and stops with error message: [ERROR] The targeted docs version "12.x-2024.10" already exist. Are you trying to update the existing snapshot? Use "npm run update-docs".

npm run update-docs

• Existing version pattern
  • Confirm that 12.x is updated based on version defined in VERSION
• New version pattern
  • Confirm that 13.x-2024.10 is updated based on version defined in VERSION

Checklist

• I've run the tests to see all new and existing tests pass
• I added automated test coverage as appropriate for this change
• Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
• If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
• I've updated the documentation if necessary

[NiklasMerz]

I'm a fan of the new versioning.