Add generic builder

[shenkeyao]

Closes EspressoSystems/marketplace-builder-core#36.
Note: This PR is to be merged to ag/builder-bin and will be merged to main as part of #1806.

This PR:

• Adds hooks for generic builder.
  • Generic builder is named as "fallback builder".
  • Existing builder is renamed as "reserve builder".
• Adds a flag to indicate the builder type upon initiation.
• Updates yaml files.

This PR does not:

• Change existing builder logic.

Key places to review:

• builder.rs.
• hooks.rs.

[QuentinI]

LGTM!

[QuentinI]

@shenkeyao @elliedavidson wdyt of making reserve and fallback non-exclusive options? I.e. allowing the builder binary to be run with any combination of those? I imagine having a --fallback flag that enables fallback behaviour, i.e. when filtering transactions also requesting list of registered namespaces and including all non-registered transactions. And if one wanted to run purely fallback builder, they'd just set namespace list to empty.

[elliedavidson]

@shenkeyao @elliedavidson wdyt of making reserve and fallback non-exclusive options? I.e. allowing the builder binary to be run with any combination of those? I imagine having a --fallback flag that enables fallback behaviour, i.e. when filtering transactions also requesting list of registered namespaces and including all non-registered transactions. And if one wanted to run purely fallback builder, they'd just set namespace list to empty.

Yes, that makes sense to me.

[shenkeyao]

@shenkeyao @elliedavidson wdyt of making reserve and fallback non-exclusive options? I.e. allowing the builder binary to be run with any combination of those? I imagine having a --fallback flag that enables fallback behaviour, i.e. when filtering transactions also requesting list of registered namespaces and including all non-registered transactions. And if one wanted to run purely fallback builder, they'd just set namespace list to empty.

Sounds good! I’ll make the change.