fix: curio: gui listen conflict

[strahe]

Related Issues

#11941

Proposed Changes

1. Change the default value of Subsystems.GuiAddress from :4701 to 127.0.0.1:4701.
2. Add a --gui-listen flag to curio run and keep it in sync with curio web.

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[LexLuthr]

Can you please rebase your PR on release/curio-beta branch and not master. All active development is current being done on release/curio-beta branch.
I am not a fan of overriding config outside of DB. This will lead us back to the old world where we had issue with config/ENV pairs.
GUI should be running only on 1 node in the whole Curio cluster which also reduces the need to override.

[strahe]

I am not a fan of overriding config outside of DB. This will lead us back to the old world where we had issue with config/ENV pairs.

I agree with that, but the listening address is not written into the database, it is specified by flag. There is a lot of flexibility when starting the service, which I think is reasonable.

GUI should be running only on 1 node in the whole Curio cluster which also reduces the need to override.

Currently, it is possible to run multiple instances, whether it's curio web or curio run, as long as the gui is added to the layers parameter. However, the listening address --listen could be ambiguous. I will submit a new PR to resolve this issue.

[LexLuthr]

@strahe Quick update. We are basing everything off of Master branch now. So, please base your new PR on master. I will backport it to the release branch once merged.
Thank you for your contributions. It is great to see community interested in Curio development. We are looking forward to the new PR.

[strahe]

@LexLuthr Could you review this first? #11965

If there are no suggestions or questions, I will rebase to master again.