Name the known swap contracts by provider and role

[0xh3rman]

Part of #1036, new Permit2 approvals look consistent (EIP712 and normal ERC20 Approve), our contract labeling shows both Uniswap (address), one of them is Permit2, another one is Router, this pr adds our known swapper contracts to scan address DB

Changes:

1. Store scan address names as " Permit2" and " Router" so the spender row tells Uniswap's Permit2 apart from its Universal Router instead of showing "Uniswap" for both.
2. Upsert the names on the (chain, address) key so a rename reaches rows already in the database on the next setup run; the fraud and verification flags stay untouched.
3. Tag the static THORChain and Maya routers, Chainflip vaults, NEAR Intents treasuries, Mayan contracts and the Squid multicall with their chain at the source, so the provider and the setup step read one table.
4. Add those addresses and the Across multicall handlers under the provider name, so history and confirmation rows show "THORChain" or "Chainflip" instead of a raw address. EVM contracts deployed at one address on every chain sit under Ethereum; the address name lookup already falls back across chains.