Better integration with `setup-dart` action for automated publishing

[tomarra]

With the push towards automated publishing of packages to pub.dev from the Dart team, they have added in the token workflow into the setup-dart action.

The workflow authenticates to pub.dev using a temporary GitHub-signed OIDC token, the token is created and configured in the dart-lang/setup-dart step. To publish to pub.dev, subsequent steps can run dart pub publish --force.

This means, for Flutter specific packages, your workflow actually has to setup Flutter and Dart which ends up being duplicative and essentially just wasting CI minutes/resources. You can see this in action in very_good_workflows -> flutter_pub_publish.

Example:

• Issue from flame_behaviors noting the hanging on authorization ci: Pub needs your authorization to upload packages on your behalf VeryGoodOpenSource/flame_behaviors#70
• PR to fix the issue adding the setup_dart step chore: update pub publish scripts VeryGoodOpenSource/flame_behaviors#75

Proposed Solutions

1. Bring the authentication step into this action. This would most likely require working with the Dart team to understand if there are any concerns with doing this or if it’s possible.
2. Allow the passing of a flag to this action to only have it setup Flutter, not Dart. Instead just assuming that Dart has been setup and is already available.

[bartekpacia]

Hey, this sounds like a good idea! I experienced this problem myself.

I'm open to accepting a PR!