Issue setting breakpoints in file uris

[connor4312]

This adds support for the "file" option in Chrome's launch.json to open
and HTML page. Support for this was straightforward. I also did some
work on the config providers to make HTML pages F5-able without needing
a preexisting launch configuration.

There's an outstanding issue where breakpoints set before Chrome is launch are sent to Chrome, but don't seem to apply. Pinged Dmitry for ideas on this, seems like some kind of race. #79

My apologies in advance if this is not the right place to post this (wanted to keep the context): Can't get to replicate this in Ubuntu 20.04.2 LTS, Linux kernel 5.4.0-74-generic SMP x86_64 GNU/Linux, VS Code 1.57.0, Debugger for Chrome (msjsdiag.debugger-for-chrome) v4.12.12 extension and Google Chrome 91.0.4472.106 (Official Build) (64-bit) - JavaScript V8 9.1.269.36. Breakpoint can't get hit and it reads Unbound breakpoint, take a look at the following image:

I'm attaching also the log file of the trace: pwa-chrome-simple-html.log

Any feedback/guideline to make it work would be appreciated. Thanks in advance!

Originally posted by @plche in #78 (comment)