fix(core): don't execute disabled dependencies

[thsig]

What this PR does / why we need it:

When executing an action that depends on a disabled dependency, the disabled dependency should be skipped (unless it's a build).

This is fixed here (in accordance with the docstring for the disabled field on action configs).

[stefreak]

Before this change, we did execute disabled actions if they were dependencies

Now the behaviour changes to silently skip executing disabled actions if other actions directly depend on them. Is that right?

I would have expected an error message or at least a warning here;

Another question that comes to my mind is if we need to treat this as a breaking change? How did 0.12 behave?

[thsig]

We did execute disabled actions if they were dependencies of a non-disabled action being processed.

Now, we only execute disabled Builds in this way, but not disabled Deploys/Tests/Runs.

This is what the docs say, and that's why this user was confused about the changed behaviour from 0.12 (where we did indeed ignore disabled dependencies).

I'm not sure whether to treat this as a breaking change, since this change means we're bringing the behaviour in line with the docs for the disabled field.

... that said, I'm also cool with holding off on merging this until the next minor/non-patch release.

[thsig]

Here's the relevant docstring that populates the reference docs for the disabled field:

garden/core/src/actions/base.ts

Lines 169 to 173 in 15b0e8d

	Set this to \`true\` to disable the action. You can use this with conditional template strings to disable actions based on, for example, the current environment or other variables (e.g. \`disabled: \${environment.name == "prod"}\`). This can be handy when you only need certain actions for specific environments, e.g. only for development.
	For Build actions, this means the build is not performed _unless_ it is declared as a dependency by another enabled action (in which case the Build is assumed to be necessary for the dependant action to be run or built).
	For other action kinds, the action is skipped in all scenarios, and dependency declarations to it are ignored. Note however that template strings referencing outputs (i.e. runtime outputs) will fail to resolve when the action is disabled, so you need to make sure to provide alternate values for those if you're using them, using conditional expressions.

[stefreak]

I think if this was what the documentation said and how 0.12 behaved like, then we should move forward with this and merge 👍 Thanks for the clarification @thsig

[stefreak]

Good work, LGTM 👍