Add docker container flows

[joroshiba]

Builds and pushes images for astria-conductor and astria-sequencer-relayer.

Images will be pushed to the astriaorg/conductor and astriaorg/sequencer-relayer package repositories respectively.

Fixes #42

[SuperFluffy]

I think the filtering strategy will cause issues.

Also the filtering for arm64 is no longer necessary.

I lean bothways when it comes to the tags (i.e. release a global tag for all images to ensure they play together vs. tagging the services/binaries individiually). I can see the lock-step as being an advantage.

[joroshiba]

I lean bothways when it comes to the tags (i.e. release a global tag for all images to ensure they play together vs. tagging the services/binaries individiually). I can see the lock-step as being an advantage.

@SuperFluffy My argument here would be that using a single tag to release all packages breaks semantic versioning.

Practically, sequencer-relayer and conductor are highly linked, but we need a tagging strategy that works across anything in monorepo. I don't want to release a new minor version of the sequencer and thus a new minor version of our EVM rollup even if there are no breaking changes to the EVM.

The tagging format I've gone with fits within semver regex, and I believe (could be wrong) will auto work with the tagging functionality that exists in the docker actions. I'm working on figuring out how to test this.

[SuperFluffy]

looks good to me now.