Rework asset test workflows to accept array of test commands

[busma13]

The asset-test and prerelease-asset-test workflows have a hard coded set of pnpm test commands. Elasticsearch-assets doesn't use these reusable workflows because it has one more test suite it needs to run. And now we are adding integration tests to standard-assets that will force us to use a custom workflow.

It should be possible to pass a list of test commands to the workflow, separated by the type of setup the test needs (e2e, integration, unit, encrypted, etc). Then the list will be used as a matrix for each job type. This would allow us to use the same reusable workflow for all of the assets again.

We should probably do the same type of thing for the prerelease tests, since only a few lines of the workflow are different.

[jsnoble]

we might need to invert control in order for this to work, here is an example of what this might look like

jobs:
  call-asset-test-workflow:
    uses: terascope/workflows/.github/workflows/asset-test.yml@main
    secrets: inherit

  my-extra-test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run extra checks
        run: echo "my additional test"

  all-checks-gate:
    needs: [call-asset-test-workflow, my-extra-test]
    runs-on: ubuntu-latest
    steps:
      - run: echo "All checks passed including extras"