chore: Migrate tag-service workflow to CircleCI

[janjakubnanista]

Description

Migrating tag-service manual github actions workflow to CircleCI. The setup is made a bit more complex since this project is using CircleCI's dynamic setup.

• Added an extra set of pipeline parameters that control the new tag-service job. These will be empty if the pipeline is run because of a push, they need to be specified when manually triggering a pipeline from CircleCI's UI.
  • To make the UX a bit more sturdy and nicer, these parameters are defined both in config.yml (strict definition, this definition populates the UI form for triggering pipelines) and continue_config.yml (so that they can be used in the actual job)
• Replaced inlined executors with executors definitions. This way the vm-image pipeline parameter that was used to DRY the config can be dropped

I also added mise as a dependency manager. mise is being used in the optimism monorepo and provides a great way of managing tooling required for development.

It is an add-on, it does not break or affect any existing development flows, just provides a convenient way of setting up your development environment (as well as the CI environment).

Tests

Please describe any tests you've added. If you've added no tests, or left important behavior untested, please explain why not.

Additional context

Add any other context about the problem you're solving.

Metadata