Creation of Configuration Profiles

[non-fungible-nelson]

Description

As a user, I want a --profile flag that I can set to easily overwrite some defaults. This way, as a new user I can only set one flag and have a good experience out of the box and get familiar with operating Besu more quickly.

Acceptance Criteria

• New configuration option --profile=string
• This flag, when set, overrides the defaults in the client with new ones from the parsed profiles.
• The profiles flag accepts the following profiles (expanded on in other tickets):
  • selfish-staker Creation of minimalist-staker profile #6324
  • staker Creation of staker profile #6325
  • private network && enterprise (both should alias to the same profile) Creation of private-network/enterprise profile #6326
• Any configuration options explicitly set in the config file or command line should overwrite any of the defaults set via the profile (i.e. private network defaults to sync-mode=FAST, if a user sets sync-mode=FULL, then the sync mode should be full

[Gabriel-Trintinalia]

@non-fungible-nelson The initial implementation of this did not consider validation between the flags. I can see that the profiles have some conflicting changes. For example, we cannot have Bonsai and prune-enabled at the same time, or the legacy transaction pool options and sequential transaction pool. The currently implementation of this issue loads all the configuration related to the profile from a toml for simplicity. What would you like to do it here? To keep the conflicting options per profile will introduce a more complex logic to this issue.