feat: simplify the input interface

[kettanaito]

This pull request reflects on a larger discussion about the GitHub Action.

Changes

• Removes all granular action inputs. Instead, a single command input should be used.
• Removes the report action. I'd not have any implicit behaviors, especially when they deviate from the raw CLI experience. The users can use the --output flag to generate the report and access it in the file system since they know the path already.
• Removes usage examples from README.md. Directs to the appropriate page in the docs. We shouldn't duplicate these examples, let them live in a single place. Easy to find, easy to manage.
• Adjusts the test workflow.
• Adds a new test to ensure that the generated report can be accessed by other steps of the job (e.g. to manipulate it, upload it as an artifact, etc).

[bernardobridge]

if I understand this correctly, you're trying to set output to always be the same hardcoded value, right? Aren't you missing the --output flag then?

Also the artillery report default format is .json.

[kettanaito]

I was thinking about this and decided that it's not a good idea to introduce this implicit behavior for the action alone. The regular run command doesn't produce any implicit reports, neither should the action. Let the usage be identical, no matter if you're using an action or tapping into the CLI directly.

[bernardobridge]

How would a user extract a report from the Github Action though? We might want to showcase this in an example

[kettanaito]

What do you mean by "extract"?

One of the ways they may want to operate with the generated report is by uploading it as an artifact on the workflow to observe after the run.

- uses: artilleryio/action-cli@v1
  with:
    command: run test.yml --output report.json

- uses: actions/upload-artifact@v3
  with:
    name: artillery-report
    path: report.json

I believe we have this example in the docs. If we don't, I will add it once we publish the action.

[kettanaito]

One good point from this is we should add an automated test to ensure the report written in the Docker image is actually available outside of the step 💯 Will add that.

[kettanaito]

Added a basic test that the generated report exists in the file system. Waiting for it to pass...

Edit: Confirm that the generated report is accessible further into the job! ✅

[hassy]