DApps: Address the security concern to show eTLD+1 of max 255 characters (site+domain) and show site origin in Panels

[Pavneet-Sing]

Description

• Update the android implementation and UI for eTLD+1 (site+domain) in brave_permission_dialog layout and delegate as per eTLD+1 standards. The 255 chars limit should have no issue but verify it with real data [-done].
  Make sure the discussed details are being shown.
• Show origin on all request panels, equivalent to desktop issue Display origin when performing actions in Brave Wallet (signing transactions etc.) #21904 or iOS Show eTLD+1 prominently in request panel brave-ios#5188

Steps to reproduce

1. Create a DApp wallet connectivity request with lengthy eTLD+1
2. A eTLD+1 with 255 chars (max) is not bold and origin is not displayed

Actual result

A eTLD+1 is not bold in DApps permission panel and origin is not displayed

Expected result

• Show eTLD+1 should be bold and completely visible
• Origin info should be displayed

Issue reproduces how often

Not yet merged in master

Version/Channel Information:

• Can you reproduce this issue with the current Play Store version? NA
• Can you reproduce this issue with the current Play Store Beta version? NA
• Can you reproduce this issue with the current Play Store Nightly version? NA

Additional information

Also add/replace the root view with ScrollView for lengthy values.

cc: @diracdeltas

[diracdeltas]

@Pavneet-Sing actually the maximium allowed length for a label in DNS is 63 characters. so eTLD+1 won't be much more than ~70 characters total.

we should always make sure to show the eTLD+1 clearly so that it's visible without any scrolling.

for subdomains, which can be a lot longer, scrolling makes sense to me

cc @darkdh @nuo-xu

[diracdeltas]

and actually the total length of the domain should be <255 characters according to the DNS spec; however i'm not sure if there are workarounds. https://serverfault.com/questions/580249/is-there-a-maximum-subdomain-depth

[Pavneet-Sing]

Got it, then length of 255 character will not be a concern on Android without scroll. Possible UI adaption could be is to show a warning or something, when the length exceeds then we can make the whole screen scroll able and keep the whole domain and subdomain sections visible (instead of defining a specific height of the domain and subdomain section).

[kjozwiak]

The above requires 1.40.78 or higher for 1.40.x verification 👍

[srirambv]

Verification passed on Oppo Reno 5 with Android 12 running 1.40.101

• Verified steps from brave/brave-core#12701
• Verified eTLD+1 is shown prominent on panel
• Logged #23513

Connect Account	Approve Tx	Approve Network	Switch Network	Sign Message	Encryption message

Verification passed on Samsung Tab A with Android 10 running 1.40.101

• Verified steps from brave/brave-core#12701
• Verified eTLD+1 is shown prominent on panel
• Encountered #23513 & #23514

Connect Account	Approve Network	Switch Network	Connected State	Sign Message	Encryption message