[google_identity_services_web] - Enhance maybeEnum to handle if enum value is not exist with a return of null.

[Hamza-Nasser]

The old maybeEnum was throwing a transitive ArgumentError that is being thrown from the extension function EnumByName::byName if the string value does not match any, now it is returning null instead.
This PR also have a new test file for the maybeEnum function with different test cases.

Fixes flutter/flutter#166548

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under¹.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩² ↩³

[ditman]

Thanks for the fix! I would have landed this, but else beat you to the punch with this fix, here: #8999 (we should have assigned them the underlying issue, sorry!)