Add a way to inject environment variables for deployment

Status quo:

• Write an .env file in a previous action step, and have this action pick that file up

Ideas:

• Just pass through all environment variables of the action. Probably a very bad idea.

• Add an environment input to the action:

  - name: Deploy to Mittwald Container Hosting
    uses: mittwald/rp-container-deploy-action@master
    with:
      mittwald-api-token: ${{ secrets.MITTWALD_API_TOKEN }}
      mittwald-project-id: 'p-XXXXXX'
      environment: |
        FOO=BAR
        BAR=${{ secrets.BAR_SECRET }}
  

No source files or tests are named. Start by locating the action's input definitions and the deployment entry point, then compare the existing .env-file handling with the proposed environment input. Done means the YAML example passes variables, including secrets, into the deployed container without requiring a previous step.