Can Dart DevTools Extension detect if source maps are enabled in Chrome DevTools?

Not sure where this issue should go but I will open it here and you can move it if needed.

I was just experimenting with some features in internal google3 projects. I ran some galleries locally and opened Dart DevTools via the chrome extension. I was seeing very strange behavior when I set breakpoints and reloaded. The current position was jumping all over and even stopping in comments. I finally realized that I had source maps disabled in Chrome DevTools. When I enabled source maps and reloaded Dart DevTools everything worked as expected.

Is there a way we could detect this situation and warn the user that they need to be enabled?

cc @elliette

No files, tests, or entry points are named. Start by locating the Dart DevTools Chrome extension integration and determine whether it can observe Chrome DevTools source-map settings; done means warning users when source maps are disabled.

Written by the indexing model from the issue text.