Improve token name filtering and formatting for Runes tokens bridged with Pontis

[markmhendrickson]

Two current problems:

1. Bridged tokens may inadvertently trigger our TLD-based filter for suspicious tokens (e.g. DOG.GO.TO.THE.MOON given the TLD .to), leading to the need to manually allowlist such tokens, incurring operational overhead and temporary UX issues before we notice and allowlist specific tokens
2. Tokens appear with periods instead of the originally intended middots per the Runes protocol (DOG.GO.TO.THE.MOON instead of DOG•GO•TO•THE•MOON)

We could resolve these issues by checking all Stacks FT names against a reliable API service that verifies known Runes token names, perhaps verifying against only those Runes tokens that have a significant market cap (to prevent bridge-based suspicious token attacks in which an attacker deploys and bridges a Runes token with a phishing URL in its name). If the Stacks FT name is verified in this way, we can override our suspicious token filter and show the name even if it otherwise matches a TLD, and we can also automatically convert the name's periods to middots.

[linear]

LEA-2128 Improve token name filtering and formatting for Runes tokens bridged with Pontis