Bens: metadata and multiprotocolling

[sevenzing]

Brief description

• Need to enhance the bens by adding "metadata" for each domain name protocol (e.g., ENS, Genome)
• Additionally, we need to update the relationship model between Blockscout instances and protocols to support a many-to-many relationship (like add way to specify which protocols should be used for every blockscout in config). Currently, each Blockscout instance is associated with exactly one protocol.
• Ignore resolving address if they start with 32 zeros (rootstock enhance)

Tech

Add Metadata for Domain Name Protocols:

Extend the domain name protocol model to include the following metadata fields:

• short_name (String): A short identifier for the protocol.
• title (String): The full title of the protocol.
• description (String): A brief description of the protocol.
• icon_url (Optional String): A URL pointing to the protocol's icon.
• docs_url (Optional String): A URL linking to the protocol's documentation.
• tld_list (List of Strings): A list of top-level domains (TLDs) associated with the protocol, for example [".eth", ".gno"]

Add this info in domain_name response

Add endpoint to get all protocols

Update Relationship Model:

• Modify the existing relationship between Blockscout instances and protocols to support a many-to-many relationship in config file.

• Update the API and backend logic to handle multiple protocols for a single Blockscout instance and vice versa.

[sevenzing]

Implemented in #890

[sevenzing]

Figma design

https://www.figma.com/design/ErLH8qySSkpprB87H0onWw/Blockscout_Pages?node-id=13789-179402&t=T1wuuauQwdkCTKpZ-0

Staging deployment links

• blockscout url: https://eth-sepolia.blockscout.com
• name example: https://eth-sepolia.blockscout.com/name-domains/vitalik.eth
• service url: https://bens-rs-test.k8s-dev.blockscout.com/
• example: https://app.warp.dev/block/Tv5z3wEyR208akX8ebI14b