feat(docs): add latest release versions for Android and iOS platform guides

[GitToTheHub]

Platforms affected

• Android
• iOS

Motivation and Context

• It good to know, what is the maximum minor/patch version for a major
• Generated-By: GPT-5.3-Codex

Description

Testing

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

[dpogue]

Not really a fan of this because it's yet another (third) thing that someone needs to remember to update when making a release, which means it will get missed and have outdated information.

[GitToTheHub]

It's true, that on a release this would have to be updated like when cordova-ios 8.1.0 would be released. If cordova.apache.org would support NPM badges by shields.io, which it currently not does, like it can be seen for cordova-plugin-network-information due to CSP erros:

Refused to load https://img.shields.io/npm/v/cordova-plugin-network-information/latest?label=Latest%20Release%20(npm) because it appears in neither the img-src directive nor the default-src directive of the Content Security Policy.

this could be automated like already done on the README for the platform e.g. cordova-ios.

If a major would be created, cordova-docs has to be anyway updated for it, but the npm badge would have to move to the next major.