Draft: Require ray for dev

What does this MR do?

It adds spatie/ray via composer for require-dev: https://spatie.be/products/ray

I saw many people struggling with xdebug in Slack, so ray might be an alternative to some people. (Well, me at least! 😉)

How confident are you it won't break things if deployed?

100% since it's just require-dev, but ray is even able to run in production without any issue.

How to test

Steps a reviewer can take to verify that this MR does what it says it does e.g.

1. Download and install the app: https://spatie.be/docs/ray/v1/the-ray-desktop-app/download-the-free-demo
2. Add a ray.php to root if using docker: https://spatie.be/docs/ray/v1/environment-specific-configuration/docker
3. Put ray('Ray is awesome!'); anywhere in (executed) php code.
4. Be happy, no struggle with xdebug setup 😊
5. See what awesome stuff ray has to offer: https://spatie.be/docs/ray/v1/introduction

Checklist

• added a test, or explain why one is not needed/possible...
• no unrelated changes
• asked someone for a code review
• set a "for:" label to indicate who will be affected by this change
• use "state:" labels to track this MR's state until it was beta tested
• added an entry to CHANGELOG.md
• add a short text that can be used in the release notes
• Once your MR has been merged, you are responsible to create a testing issue in Beta Testing Repo:
  • Consider writing a detailed description in German.
  • Describe in a few sentences, what should be tested from a user perspective.
  • Also mention different settings (e.g. different browsers, roles, ...). how this change can be tested.
  • Be aware, that also non technical people should understand.

Release notes text

Added https://spatie.be/products/ray for composer dev install