Summary

support launch editor feature

Original Feature Request #20435

When you inspected a react component, you can click the launch editor icon to jump to your editor and navigate to the source code original file position.

supoort set custom launchEditorEndpoint

Why we need this ? Because different launch editor server middleware use different endpoint.

create-react-app user must use __open-stack-frame-in-editor as endpoint cause these hard code.

https://github.com/facebook/create-react-app/blob/master/packages/react-dev-utils/launchEditorEndpoint.js#L9-L10

// TODO: we might want to make this injectable to support DEV-time non-root URLs.
module.exports = '/__open-stack-frame-in-editor';

launch-editor-middleware user often use __open-in-editor as endpoint.

https://github.com/yyx990803/launch-editor#middleware

const launchMiddleware = require('launch-editor-middleware')
app.use('/__open-in-editor', launchMiddleware())

Both middleware have many user around world (and exist many custom middleware actually).

Issues need to fix

1. Can we get the releative file path from devtools ? Now the source path is absolute(e.g. /Users/iChenLei/Documents/cra/reactapp/src/App.js:24).
2. If we only can use absolute file path, we need create pr for create-react-app/react-dev-utils to support absolute path.
   https://github.com/facebook/create-react-app/blob/master/packages/react-dev-utils/launchEditor.js#L287-L290

+ const filePath = path.relative(process.cwd(), fileName)

3. Please help me make a suitable svg icon for launch editorfeature, Thanks for facebook/react official.
4. Is there common toast ui component to show message about set custom endpoint success ? I think feedback is necessary.

@bvaughn Sir, I need your code review and advices, thanks.

I must say that it's too hard for me to run the devtools extension build and test script, many network error / script error and other problems, It drives me crazy 😭 .

Test Plan

will add necessary unit test later