add environment input to support github deployment environments

[jakemac53]

Closes #130

Separates publish/validate into two different jobs. The publish job will use the supplied environment, which may require approvals to run the jobs if configured. See https://dart.dev/tools/pub/automated-publishing#hardening-security-with-github-deployment-environments.

[github-actions]

PR Health

Package publish validation ✔️

Details

Package	Version	Status
package:firehose	0.3.22-wip	version 0.3.22-wip is pre-release; no publish necessary
package:dart_flutter_team_lints	1.0.0	already published at pub.dev

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

License Headers ✔️

Details

// Copyright (c) 2023, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Files
no missing headers

All source files should start with a license header.

Changelog Entry ✔️

Details

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

Coverage ✔️

Details

File	Coverage

This check for test coverage is informational (issues shown here will not fail the PR).

[devoncarew]

lgtm

Before landing, please update the changelog + pubspec (to either 0.3.22-wip or 0.3.22); thanks!

[devoncarew]

I assume this is a no-op if inputs.environment is empty / not specified?

[jakemac53]

I do assume so although I haven't found documentation on it. This is how the core dart-setup publish action works though.