HTTP Compression for Artifacts cannot set to Disable for specs plan

HTTP Compression for Artifacts cannot set to Disable when using specs to manage plan.

For plans created manually, HTTP compression can be set to Disable by unchecking the Compression option in the Artifact definition.

Steps to Reproduce:

1. Create a Bamboo Plan with Specs(YAML) and define the artifact in the Specs configuration with httpCompressionOn: false

   .
   .
   artifacts:
   - name: Hello Javaparser
     location: target/classes/com/yourorganization/maven_sample
     pattern: '*.class'
     shared: true
     required: true
     httpCompressionOn: false
   .
   .
   

2. No errors are detected during Specs scan for the parameter httpCompressionOn.
3. When build is executed, we can still see the HTTP compression is enabled for the Artifact.

   simple	18-Mar-2024 13:09:58	Publishing an artifact: Hello Javaparser
   simple	18-Mar-2024 13:09:58	Finished publishing of artifact Required shared artifact Http Compression On : [Hello Javaparser], patterns: [*.class] anchored at: [target/classes/com/yourorganization/maven_sample] in 128.1 ms
   

Expectation:

The HTTP compression should be Off as in case of manually created plan. Ex:

simple	11-Mar-2024 15:25:57	Publishing an artifact: Hello Javaparser
simple	11-Mar-2024 15:25:57	Finished publishing of artifact Required shared artifact Http Compression Off : [Hello Javaparser], patterns: [*.class] anchored at: [target/classes/com/yourorganization/maven_sample] in 11.61 ms

 Workaround:

Create the plan manually in Bamboo and uncheck the Compression option in the Artifact definition of the plan.