Allow all configuration that can be set on test to be set on workflow

[muffl0n]

I have a workflow that executes several test on a staging environment that is protected via http authentication. This looks like this

version: "1.1"
name: Status Check
env:
  host: staging.example.com
components:
  credentials:
    default:
      basic:
        username: foo
        password: bar
config:
  continueOnFail: true
tests:
  api:
    steps:
      - name: api2 404
        http:
          url: https://${{env.host}}/api2
          method: GET
          auth:
            $ref: "#/components/credentials/default"
          check:
            status: 404
      - name: foo
        http:
          url: https://${{env.host}}/api2/foo
          method: GET
          followRedirects: false
          auth:
            $ref: "#/components/credentials/default"
          check:
            status: 301
            headers:
              Location: https://${{env.host}}/api3/foo
      - name: bar
        http:
          url: https://${{env.host}}/api2/bar
          method: GET
          followRedirects: false
          auth:
            $ref: "#/components/credentials/default"
          check:
            status: 301
            headers:
              Location: https://${{env.host}}/api3/bar

As one can see, specifying the authentication on every test is a tedious task. Also specifying followRedirects: false on some tasks clutters the workflow.
Is there a specific reason, why one can't specify all configuration that can be set on a test to be set on its workflow? auth and followRedirects are just two I came across. I'm sure there are a lot more.
And what about method: GET? This could also be a sane default, imho.

[mishushakov]

Agreed with the points above, especially about GET as default