New restore subscription android

[deeppandya]

Resolves brave/brave-browser#38085

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

Please reach out to @deeppandya for more details on testing

[samartnik]

lgtm

[SergeyZhukovsky]

Just a general question: how does it suppose to look when a user has mobile only purchase? Do we always show the restore button? As I don't think we can restore credentials if the account isn't linked.

[mkarolin]

strings++

[SergeyZhukovsky]

++

[github-actions]

[puLL-Merge] - brave/brave-core@23725

Description

This PR makes several changes related to subscription linking and management for the Brave browser's VPN and AI chat (Leo) features on Android. It updates UI elements on the subscription plans pages, adds new utility functions for handling subscription linking, and removes some unused code.

Changes

Changes

• android/brave_java_resources.gni: Adds a new drawable resource refresh_credentials_bg.xml
• android/java/org/chromium/chrome/browser/billing/LinkSubscriptionUtils.java: Adds new utility class with functions to get Brave account URLs for linking subscriptions and refreshing credentials, with support for staging environment
• android/java/org/chromium/chrome/browser/brave_leo/BraveLeoPlansActivity.java, android/java/org/chromium/chrome/browser/vpn/activities/BraveVpnPlansActivity.java: Adds a "Refresh your credentials" button to the Leo and VPN subscription plans pages that links to Brave account
• Various files: Updates code to use the new LinkSubscriptionUtils functions instead of hardcoded URLs
• android/java/org/chromium/chrome/browser/settings/developer/BraveQAPreferences.java:
  • Renames PREF_USE_LEO_STAGING_SERVER to PREF_LINK_SUBSCRIPTION_ON_STAGING
  • Removes isLeoStagingUsed() function
• android/java/org/chromium/chrome/browser/util/TabUtils.java: Adds openURLWithBraveActivity() utility function
• android/java/org/chromium/chrome/browser/vpn/utils/BraveVpnPrefUtils.java:
  • Removes PREF_BRAVE_VPN_LINK_SUBSCRIPTION_ON_STAGING constant
  • Removes isLinkSubscriptionOnStaging() and setLinkSubscriptionOnStaging() functions
• Various resource files: Adds/updates colors, dimensions, styles for UI changes

Security Hotspots

None found. The changes do not appear to introduce any new security risks.