[Feature]: Allow runbook parallel execution on connections with only access_mode_runbooks (but not access_mode_exec)

[LucVidal360]

Is your feature request related to a problem?

We'd like to be able to launch runbooks in parallel mode.
However, we created dedicated connections for runbooks, with only the access_mode_runbooks enabled (not access_mode_exec).

Unfortunately, the parallel mode is not allowed on connections without access_mode_exec.

hoop/webapp/src/webapp/parallel_mode/helpers.cljs

Lines 7 to 16 in b6ded8d

	(defn valid-for-parallel?
	"Check if connection is valid for parallel mode execution"
	[connection]
	(and
	;; Exclude specific subtypes
	(not (contains? db/excluded-subtypes (:subtype connection)))
	;; Must have exec enabled
	(= "enabled" (:access_mode_exec connection))
	;; Must be online
	(= "online" (:status connection))))

If it makes sense for terminal parallel mode, it's not the case for runbooks parallel mode.

Describe the solution you'd like

When selecting connections for runbook parallel mode, I'd like to be able to select any connection with at least access_mode_runbooks.

Describe alternatives you've considered

For now, we have to launch our runbooks manually on all the desired connections.

Priority

Medium - Would improve my workflow

Use Case

To deploy a new release, we need to activate:

• a set of feature flags
• on all our environments

Activating a set of flags on a single environment can be achieved with a runbook execution.
We could launch the runbook on all environments at once with parallel mode.

Mockups or Examples

No response

Additional Context

No response

Contribution

• I would be willing to submit a PR to implement this feature

Code of Conduct

• I agree to follow this project's Code of Conduct