Remove resolve-url dependency about tesseract.js HOT 1 CLOSED

It looks like we use the resolveURL function in 3 places.

1. To set different default options during development in defaultOptions.js
   1. This is only run during development; changing should not impact production code
2. To convert paths to images to absolute URLs in the browser version of loadImage.js
   1. I do not believe this serves any purpose, and intend on cutting entirely
      1. We use fetch to retrieve images--fetch can handle relative paths without any additional dependency
      2. Images are fetched on the main thread, so there is no issue with workers not knowing what page they are being run on (see below)
3. To convert corePath, workerPath, and langPath to absolute URLs in the browser version of resolvePaths.js
   1. This is presumably necessary as these paths are sometimes or always retrieved from within a worker
      1. Users likely expect all relative paths to be resolved relative to the main window rather than workers
   2. I believe this one-line function achieves this goal: s => (new URL(s, window.location.href)).href

from tesseract.js.