(fx112) Add file for ray function and update ray() in offset-path

[dipikabh]

Summary

• ray() already has a row in offset-path BCD table https://developer.mozilla.org/en-US/docs/Web/CSS/offset-path#browser_compatibility, which needs to be updated for Fx112.
• A new ray() function page is being created (docs(fx112-css-ray): Create new page for ray() function content#26266) and a new BCD table needs to be created for this. The new ray.json file also adds the spec link.

Supporting info

• I have picked most of the ray() info for the new table from the offset-path BCD table.
• Firefox: ray() is still behind the flag layout.css.motion-path-ray.enabled. In Fx112, support is added for spec's updated syntax.
• Chrome:
  • The BCD table on offset-path page contains a row on ray() that indicates complete support from Chrome 64 (added via CSS motion path updates #5045), which is contrary to what I saw in testing.
  • The last mention in Chrome on offset-path seems to have been in 64 (https://chromestatus.com/newfeatures?q=offset-path)
  • On Canary, the feature works with experimental mode enabled.
  • It was working earlier but now it does not seem to be working in Chrome 112 even in experimental mode.
  • In both offset-path and ray() json files, I have added note for Chrome support in experimental mode.
• For its status in Firefox and Chrome, I have also marked "experimental": true in ray.json file.

Test results and supporting details

The following codepens can be used to test in Firefox and Chrome:
Example 1: https://codepen.io/dipikabh/pen/yLReQaZ
Example 2: https://codepen.io/dipikabh/pen/PoyNQdz

Related issues

Doc issue tracker: mdn/content#25358
Content PR: mdn/content#26266
Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1820071
Spec: https://drafts.fxtf.org/motion/#ray-function

[dipikabh]

Thanks, @queengooborg!