chore: Add inputs to kurtosis-op workflow to override op-geth and op-node images [OPTION 2]

[janjakubnanista]

Description

• Adds a new local kurtosis job
  • Uses locally built op-node and op-geth images in kurtosis-op
  • The images are built from repositories provided when the workflow is dispatched and are not necessarily coming from the optimism and op-geth repos, a fork can be specified as a source. The repos are cloned and the requested ref is checked out dynamically
• Preserves the original remote job

Since the repos are parametrized, one must be careful about them as they could potentially cause a security breach. Don't run this action with just any repo!

Fixes #14

[emhane]

if the op-reth image can be built from a local branch instead of being downloaded that would be better.

this is such a cool open-source contribution. for example @joshieDo sometimes has an op-node branch from his fork to test with op-reth. smthg interesting to upstream? or to odyssey maybe cc @onbjerg

[janjakubnanista]

if the op-reth image can be built from a local branch instead of being downloaded that would be better.

this is such a cool open-source contribution. for example @joshieDo sometimes has an op-node branch from his fork to test with op-reth. smthg interesting to upstream? or to odyssey maybe cc @onbjerg

At the moment, all the images can be built off any git branch actually:

• op-reth image is built by the workflow and depends on which branch you run the workflow on
• op-geth repo & ref (branch/commit hash) depend on the workflow parameters, they have some reasonable defaults but can be changed to any fork/branch
• op-node repo & ref (branch/commit hash) depend on the workflow parameters, they have some reasonable defaults but can be changed to any fork/branch