Split tunnel follow up

[deeppandya]

Resolves brave/brave-browser#24576

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• 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, npm run lint, 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/Custom-Headers
  • 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:

General points for split tunnel :

1. Split tunnel should not be shown if user doesn't have any vpn profile.
2. if vpn is enabled and user tries to exclude the app and press save, VPN should be connected automatically with updated profile with out user interaction.
3. if vpn is disabled and user tries to exclude the app and press save, profile should be updated in the background. When user tries to connect to the vpn, vpn should be connected with new profile.

Plan :
Follow the same test plan from : brave/brave-browser#24576

[tapanmodh]

LGTM

[Uni-verse]

Verified on Samsung Galaxy S21 using build version:

Brave	1.45.1 Chromium: 105.0.5195.37 (Official Build) canary (64-bit) 
Revision	5f67e9f258cc28ab970e57572290edf1863ee3c5-refs/branch-heads/5195@{#621}
OS	Android 12; Build/SP1A.210812.016

VPN Enabled:

• Excluding an app and saving will update the VPN connection automatically without user interaction.
• User is able to include an app and save and VPN connection will update automatically.

VPN Disabled:

• User is able to include and exclude apps under split tunneling and the VPN connection will update automatically if user enables VPN in setting.
• User is able to include/exclude system apps.

Split Tunneling:

• Split tunneling should not be shown if user doesn't have any vpn profile.
• Verified apps in the exclude list under split tunneling will not work with the VPN.
• Verified removing apps under split tunneling while VPN is running will update the profile automatically and also have the VPN settings take effect.

Example	Example