[interactive_media_ads] Adds remaining methods for internal wrapper of the native AdsRequest

[bparrishMines]

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.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

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. ↩ ↩² ↩³

[gemini-code-assist]

Code Review

This pull request effectively expands the AdsRequest API for both Android and iOS, providing more control over ad requests. The changes are well-implemented across Dart, Kotlin, and Swift, with corresponding updates to Pigeon definitions and comprehensive tests. The upgrade to a newer Pigeon version also introduces beneficial changes for testability. I have one minor suggestion to improve the robustness of the Swift implementation by replacing a force cast with a safer conditional cast. I've referenced the Flutter style guide in my review comment.

[gemini-code-assist]

Using a force cast as! can lead to a runtime crash if the type cast fails. For better robustness and maintainability, it's recommended to use a conditional cast as? with a guard statement to safely unwrap the delegate.

        guard let proxyApiDelegate = pigeonApi.pigeonRegistrar.apiDelegate as? ProxyApiDelegate else {
          throw PigeonError(
            code: "cast-error",
            message: "apiDelegate is not of type ProxyApiDelegate.",
            details: nil)
        }
        throw proxyApiDelegate.createConstructorNullError(
          type: URL.Type.self, parameters: ["string": contentURL])

[stuartmorgan-g]

LGTM