feat: also pass securityOrigin to media permissions request handler

[mserrano]

For media requests, the handler passed to setPermissionRequestHandler seems to always get a reference to the top-level frame and the top-level URL, and is not passed the request's security_origin. For consistency with setPermissionCheckHandler's handling of this case for media requests, pass the request's security_origin as a new securityOrigin field in details to enable disambiguation.

Checklist

• PR description included and stakeholders cc'd
• npm test passes -> ran under e test --runners=main, everything seemed to behave just as it did before the change
• tests are added
• relevant documentation is changed or added
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Began passing securityOrigin in details for permission request handlers for media requests in addition to permission check handlers.

[welcome]

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[mukulhase]

@MarshallOfSound

[zcbenz]

API looks good to me.

[zcbenz]

I'm changing this from fix to feat since it changes the API interface.

[codebytere]

API LGTM

[codebytere]

I think we do want to potentially backport this cc @zcbenz

[mserrano]

My bad on the fix vs feat thing! Thanks for fixing that.

Just wanted to check in on if there was anything anyone was waiting for me for on this PR: is there anything I should be doing on this right now?

[jkleinsc]

Merging as CI failures are known flake unrelated to this PR.

[welcome]

Congrats on merging your first pull request! 🎉🎉🎉

[release-clerk]

Release Notes Persisted

Began passing securityOrigin in details for permission request handlers for media requests in addition to permission check handlers.

[trop]

I have automatically backported this PR to "15-x-y", please check out #31417

[jkleinsc]

/trop run backport-to 14-x-y

[trop]

The backport process for this PR has been manually initiated - sending your PR to 14-x-y!

[jkleinsc]

/trop run backport-to 13-x-y

[trop]

The backport process for this PR has been manually initiated - sending your PR to 13-x-y!

[trop]

I have automatically backported this PR to "14-x-y", please check out #31436

[trop]

I have automatically backported this PR to "13-x-y", please check out #31437