Update Maven Central publishing from OSSRH to Central Portal.

[brandonpage]

These changes allow us to publish to the new Maven Central Portal via the OSSRH Staging API, which is documented as:

The Portal OSSRH Staging API is a partial reimplementation of the OSSRH / Nexus Repository Manager 2 Staging APIs. The intent of this service is to enable publishers who are using existing plugins to have a smooth migration to the Central Publisher Portal. We hope that over time plugins will adopt the Portal API rather than rely on this service.

It does not sound like this intermediate API is going away anytime soon, but we should eventually upgrade to the new API when the Gradle Plugin we use supports it or an official Gradle Plugin is finally released.

[brandonpage]

This last line is needed tell the staging API we are done and ready to validate in the new Central Portal.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.06%. Comparing base (b2aa153) to head (1188837).
⚠️ Report is 2 commits behind head on dev.

Additional details and impacted files

@@             Coverage Diff              @@
##                dev    #2753      +/-   ##
============================================
+ Coverage     55.88%   56.06%   +0.17%     
- Complexity     2474     2492      +18     
============================================
  Files           211      211              
  Lines         17259    17259              
  Branches       2413     2413              
============================================
+ Hits           9646     9677      +31     
+ Misses         6557     6532      -25     
+ Partials       1056     1050       -6     

Components	Coverage Δ
Analytics	47.92% <ø> (ø)
SalesforceSDK	43.86% <ø> (-0.10%)	⬇️
Hybrid	58.05% <ø> (-0.41%)	⬇️
SmartStore	78.20% <ø> (ø)
MobileSync	79.23% <ø> (+1.61%)	⬆️
React	45.97% <ø> (-0.98%)	⬇️
see 11 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.