Brainstorming and Make Faucet Key and proposal faucet Independent

[kneerose]

Description

• The current implementation relies on the availability of a faucet key and proposal faucet wallet secrets, which may not be accessible to all developers or environments. This tight coupling introduces limitations in testing and automation scenarios. The goal is to brainstorm and implement changes that make the faucet key and proposal faucet secret optional or independent, improving developer experience and system robustness.

Possible Fixes

Idea 1

• Automatically generate a new wallet and allow developers to fund it manually if the faucet key is unavailable.
• Detect the faucet wallet and skip related tests if the wallet has insufficient balance.
• Document the new flow in the README, including setup, funding, and configuration steps.

Idea 2

• Add environment variables for the required faucet address and secrets.
• Detect the faucet wallet from environment variables and skip related tests if the wallet setup is failed.
• use single faucet wallet from environment variable and remove proposal faucet and generated faucet wallet
• Refund any unspent amount to the provided faucet address.
• Document the new flow in the README, including setup, funding, and configuration steps.
• Skip test cases if the auth setup is not available, which is dependent on that test
• Remove all JSON files generated during the test

[kneerose]

• Generated report for faucet setup
  https://cardanoapi.github.io/govtool-test-reports/govtool-frontend/176/#behaviors

[kneerose]

• Refactor: project structure IntersectMBO/govtool#3564
• Allure Report