Prepare manual vcpkg release updates for minimal SQLite and Android curl

[bmehta001]

Why

The SDK overlay already declares minimal-sqlite and android-curl-openssl, but the official vcpkg port does not expose them. A version-only registry bump would leave its manifest and feature wiring behind. Prepare the complete port manually after the next SDK release rather than requiring a personal token for release-triggered PR automation.

Changes

• Remove the automated vcpkg-release-bump.yml workflow and its PAT/fork configuration requirements.
• Promote the complete overlay port from the release tag using a manual helper, including its manifest, CMake wiring, and any patches, before updating the release version and archive hash. Remove obsolete port files and reset port-version.
• Add a token-free preparation helper for the manual vcpkg PR after the next SDK release. Validate the required features, release metadata, and destination before replacing the registry port.
• Preserve the default consumer graph while adding Linux minimal-SQLite coverage and Android default, minimal-SQLite Java/JNI, minimal-SQLite curl/OpenSSL, and minimal-SQLite curl/mbedTLS build variants.
• Document current registry feature availability and the manual release promotion procedure in both the vcpkg guide and maintainer onboarding.

This PR does not cut a release, change the currently published registry port, configure a release token, or open a vcpkg PR. Merge it before cutting the next SDK release; the subsequent registry PR can then expose these features with matching released source.

Validation

• Six release-port regression tests pass on Windows and Linux/WSL, with no skipped or excluded tests.
• The remaining modified workflow passes actionlint; shell syntax checks and the repository's misspell check pass for the changed documentation and scripts.
• The consumer manifest is formatted using vcpkg format-manifest.
• Full Linux/Android port builds are covered by the expanded PR CI matrix; they were not run locally.