Apply presets before applying defaults (#2778)

## Why
Presets should have more priority and need to see the configuration
before common defaults are applied, because this mutator is making
decisions based on presence of user-provided fields in the
configuration.

This does not matter currently where we only have few defaults, but will
start to matter once we add more, like in
#2767

Previous PR #2777 makes it
possible to move this without issues.

## Tests
Existing tests for empty resource added in
#2771 and
#2774

Author: denik

bundle/config/mutator/resourcemutator/resource_mutator.go

@@ -35,6 +35,9 @@ func applyInitializeMutators(ctx context.Context, b *bundle.Bundle) diag.Diagnos
 		// OR corresponding fields on ForEachTask if that is present
 		// Overrides job compute settings with a specified cluster ID for development or testing
 		OverrideCompute(),
+
+		// ApplyPresets should have more priority than defaults below, so it should be run first
+		ApplyPresets(),
 	)
 
 	if diags.HasError() {
@@ -58,8 +61,6 @@ func applyInitializeMutators(ctx context.Context, b *bundle.Bundle) diag.Diagnos
 	}
 
 	diags = diags.Extend(bundle.ApplySeq(ctx, b,
-		ApplyPresets(),
-
 		// Reads (typed): b.Config.Resources.Jobs (checks job configurations)
 		// Updates (typed): b.Config.Resources.Jobs[].Queue (sets Queue.Enabled to true for jobs without queue settings)
 		// Enable queueing for jobs by default, following the behavior from API 2.2+.