Test behavior using only job.environment configuration

[Firehed]

No description provided.

[Firehed]

Learnings here: there's (as of writing) completely undocumented behavior that if you use the workflow environments feature (jobs.id.environment), it will automatically create and update the status of a deployment.

https://github.community/t/using-github-actions-environments-without-creating-deployment/168426

While it would be ideal to hook into there (both pragmatically and to benefit from stuff like secret management), nothing I've seen looking through the logs makes it appear accessible in any practical way, and it seems to lead to conflicts more often than not.

At least until the features and/or API mature, I think it's necessary to recommend avoiding the feature in combination with this action for now. If it becomes possible to use the created deployment and take over its status updates, I'll re-evaluate that position; ideally, it would actually be the default behavior (which would probably necessitate a breaking change)