Fetch tags for version command

[dnfield]

Description

Fetch upstream tags as part of the version command.

Related Issues

Fixes reported issues in #14230
See also #52062

Tests

I added the following tests:

Assert that flutter version calls the fetchAndUpdateTags on the global flutterVersion.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I signed the CLA.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Did any tests fail when you ran them? Please read Handling breaking changes.

• No, no existing tests failed, so this is not a breaking change.

[jonahwilliams]

See L70:

We're recommending that users not invoke the version command, and personally I'd like to remove it if possible in a future release

[jmagman]

LGTM.
@jonahwilliams this command probably isn't going away any time soon...

[jonahwilliams]

FWIW It isn't on part of the main upgrade/downgrade workflow and we have no obligation to maintain it otherwise.

[dnfield]

This should at least be an incremental improvement that's fairly easy to apply. The command definitely still has issues and needs more work or to be removed (and probably clearly deprecated first).

I think we could probably deprecate it as long as we had some good story about what to use instead.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.