feat(puck context):added iframe ref to the puck context

[IMythx]

added iframe ref to the puck context for the sake of accessing the iframe.contentWindow, iframe.contentDocument and listening to events...etc

potential use cases

1-

iframeRef?.current?.contentWindow?.matchMedia(...)?.matches

to give us the ability to create useMediaQuery custom hook inside the iframe which is differnet than doing it on the global window object (personally faced that case)

2-

iframeRef?.current?.addEventListener('load', (e)=>{
//update some elements or do something
})

and of course many other potential cases

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
puck-docs	✅ Ready (Inspect)	Visit Preview	Oct 11, 2024 11:03pm

[vercel]

@IMythx is attempting to deploy a commit to the Measured Team on Vercel.

A member of the Team first needs to authorize it.

[IMythx]

Closes #640

[chrisvxd]

Hmm, not sure if we actually need this - the Puck iframe does have a unique ID, so this could easily done by using #preview-frame selector.

[IMythx]

Hmm, not sure if we actually need this - the Puck iframe does have a unique ID, so this could easily done by using #preview-frame selector.

oh i just noticed that unique id!
but what if it got changed in the future?? i mean there is no explicit indicator that someone is using this id

[chrisvxd]

Yeah, that's a valid concern, and why I haven't closed this.

I think this PR requires a bit more consideration because it adds 2 new APIs (iframe ref in usePuck, and iframe.ref prop to Puck component). Hopefully the selector should help for the time-being.