feat: inject source location data to Slice usage and show errors in places where user renders them and not in gatsby internals

[pieh]

Description

React component stack trace is not always showing source code location (see https://github.com/facebook/react/blob/2cf4352e1c81a5b8c3528519a128c20e8e65531d/packages/shared/ReactComponentStackFrame.js#L135-L137 ).

This makes it hard to show a relevant codeframe from the user when we are throwing validation errors inside gatsby / slice placeholder component internals as we would point to gatsby internals which is irrelevant to users.

This PR:

• add babel plugin to add __renderedBylocation prop to all stages aside from build-javascript
• adds error.forcedLocation on slice validation errors
• adjusts dev overlay to use error.forcedLocation if provided (and fallback to inspecting stack trace if not) - this also needed dev server adjustments to handle cases where location is already one from source code and not the compiled code.
• adjusts createErrorFromString function to be able to receive entire error object and not just error.stack (it's backward compatible, it still handles passing stack in) to make use of error.forcedLocation if available

Results:

gatsby develop (regular, client-only rendering):

gatsby develop (with DEV_SSR enabled)

Same overlay as in develop + following in terminal:

gatsby build:

[ch56637]