Adds export conditions

[marklundin]

This PR adds development and profiler export conditions to the package.json.

Libraries the implement the engine cannot easily provide a way for end users to select different engine builds. Given the following use case its not possible to select the dev build:

1. User imports @playcanvas/react.
2. User makes a WGSL shader.
3. User needs better debug information from playcanvas about shader compilation.

This is not a new problem. Node has introduced export conditions (already used for import/require). This allows users to select versions of a lib globally

node --conditions=development index.js 

In addition Modern dev environments (Webpack, Vite, Rollup, Parcel) feed those conditions automatically, meaning that by default in local dev mode you get the development version, and running npm run build will automatically export the production version.

I have kept the original ./debug export paths etc, but unless needed by examples or other tooling these could be removed.

[mvaligursky]

This feels good!

[kpal81xd]

Nice yea just check it works in other tools like svelte etc I remember us having some import issues there. Keep the old paths in for now I feel like they may be used in the examples not sure tho

[marklundin]

Yep, let's leave them in for now. It's optional step for bundlers, so I expect it won't work in all, but for those that do, it's a better dev experience.