[quick_actions] Update "eponymous concept" link.

[happy-san]

Description

Umm, a measly link update.

Related Issues

--

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
• I updated CHANGELOG.md to add a description of the change.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[happy-san]

@googlebot I signed it!

[mvanbeusekom]

LGTM!

[bparrishMines]

LGTM

[stuartmorgan-g]

Unfortunately this never landed, and now has a conflict. If you can update and resolve (it may just be the file move), we can get this landed.

#2851 is the same fix; whichever gets updated can be landed and the other closed.

[happy-san]

Hey, @stuartmorgan do I rebase this against master?

[stuartmorgan-g]

I'm re-running the failed CI jobs since they were network/server issues, then it should be good to land. Thanks for updating!

(Normally we'd do a version bump so we could publish, but I expect this plugin to have other updated published relatively soon so we can just pick it up then.)

[stuartmorgan-g]

Re-run of Windows Plugins was successful, but LUCI doesn't update GitHub status still, so landing.