fix: link transaction hash directly and clarify queued copy

[3alpha]

What

Improves the "Release queued" screen shown after publishing.

• The transaction hash is now the Etherscan link itself, instead of a separate "navigate here" link.
• Reworded the queued message so it does not imply a scheduled processing order.
• Renamed the component and its props from IntroductionStep to ReleasePublished to match the file.
• Replaced toLocaleLowerCase() with toLowerCase() for repo addresses.
• Added an optional className prop to the shared Link component.

Why

The transaction hash was displayed as plain text with the actual link hidden behind a separate "here" link. Making the hash clickable is clearer and removes the redundant sentence.

The previous copy ("processed sooner or later based on the gas fee you provided") read as outdated and implied a scheduled processing order. A queued transaction is not processed on a schedule; it is included in a block once its gas fee becomes competitive, so the copy now says that directly.

Notes

• toLocaleLowerCase() is locale-sensitive and is the wrong tool for lowercasing an address.
• break-all was added to the hash link so the 66-character hash wraps instead of overflowing the card.

Verification

• npx tsc --noEmit passes with no errors.

• The app was run locally and the screen was rendered and screenshotted. Rendered output:

  Release queued

  Your transaction has been queued successfully. It will be included in a block as soon as the gas fee you set becomes competitive, so it may take a while.

  Transaction hash: 0xa2b9acdf...a83f77

  You can also browse the published hash in the DAppNode Explorer.

[github-actions]

🚀 Deployed on https://6ac3db2f82a4729fbffb04b0--competent-leavitt-8f172d.netlify.app