[Faucet][CLI] Add message to indicate faucet is starting

[banool]

Description

Small quality of life improvement. This way users can tell that the faucet hasn't actually started yet.

Test Plan

$ cargo run -p aptos -- node run-local-testnet --force-restart --with-faucet --assume-yes
Completed generating configuration:
        Log file: "/Users/dport/.aptos/testnet/validator.log"
        Test dir: "/Users/dport/.aptos/testnet"
        Aptos root key path: "/Users/dport/.aptos/testnet/mint.key"
        Waypoint: 0:645b3a18445fbb7ae17031b2e5f14929bfbf8d5612acdd668be2a6824c31ea0d
        ChainId: testing
        REST API endpoint: http://0.0.0.0:8080
        Metrics endpoint: http://0.0.0.0:9101/metrics
        Aptosnet fullnode network endpoint: /ip4/0.0.0.0/tcp/6181

Aptos is running, press ctrl-c to exit

Faucet is starting, please wait...
Faucet is running. Faucet endpoint: http://0.0.0.0:8081

[github-actions]

✅ Forge suite compat success on aptos-node-v1.4.4 ==> 54975f86d58a7ac108dc7a3d6ba22147ad111e9e

Compatibility test results for aptos-node-v1.4.4 ==> 54975f86d58a7ac108dc7a3d6ba22147ad111e9e (PR)
1. Check liveness of validators at old version: aptos-node-v1.4.4
compatibility::simple-validator-upgrade::liveness-check : committed: 6667 txn/s, latency: 4838 ms, (p50: 4800 ms, p90: 7000 ms, p99: 8100 ms), latency samples: 233360
2. Upgrading first Validator to new version: 54975f86d58a7ac108dc7a3d6ba22147ad111e9e
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 3639 txn/s, latency: 8495 ms, (p50: 9500 ms, p90: 10800 ms, p99: 11500 ms), latency samples: 145560
3. Upgrading rest of first batch to new version: 54975f86d58a7ac108dc7a3d6ba22147ad111e9e
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 4094 txn/s, latency: 7622 ms, (p50: 7900 ms, p90: 9600 ms, p99: 10600 ms), latency samples: 163760
4. upgrading second batch to new version: 54975f86d58a7ac108dc7a3d6ba22147ad111e9e
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 6561 txn/s, latency: 5011 ms, (p50: 5000 ms, p90: 7200 ms, p99: 8700 ms), latency samples: 236220
5. check swarm health
Compatibility test for aptos-node-v1.4.4 ==> 54975f86d58a7ac108dc7a3d6ba22147ad111e9e passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite land_blocking success on 54975f86d58a7ac108dc7a3d6ba22147ad111e9e

performance benchmark : committed: 5478 txn/s, latency: 7256 ms, (p50: 6600 ms, p90: 9900 ms, p99: 20100 ms), latency samples: 2339519
Max round gap was 2 [limit 4] at version 2387896. Max no progress secs was 4.575823 [limit 10] at version 2387896.
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite framework_upgrade success on aptos-node-v1.4.4 ==> 54975f86d58a7ac108dc7a3d6ba22147ad111e9e

Compatibility test results for aptos-node-v1.4.4 ==> 54975f86d58a7ac108dc7a3d6ba22147ad111e9e (PR)
Upgrade the nodes to version: 54975f86d58a7ac108dc7a3d6ba22147ad111e9e
framework_upgrade::framework-upgrade::full-framework-upgrade : committed: 4563 txn/s, latency: 6982 ms, (p50: 6300 ms, p90: 10500 ms, p99: 21500 ms), latency samples: 177980
5. check swarm health
Compatibility test for aptos-node-v1.4.4 ==> 54975f86d58a7ac108dc7a3d6ba22147ad111e9e passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking