Customize gateway from bos.config.json

[elliotBraem]

bos-workspace supports a custom gateway via a -g flag and either a local file path, or a url to nearfs bundle or CDN. We want to be able to configure this from bos.config.json

Add a "gateway" section to the bos.config.json

I'm thinking something like this:

{
  "gateway": {
    "tagName": "near-social-viewer", // element tag
    "bundleUrl": "https://ipfs.web4.near.page/ipfs/bafybeifvti4qqgrjnyzdzueitruup6rnqwasxt742stdyby2xey3ymnhie", // path to dist
  }
}

Although, also considering a version like this:

{
  "gateway": {
    "tag": "near-social-viewer", // element tag
    "source": "https://ipfs.web4.near.page/ipfs/bafybeifvti4qqgrjnyzdzueitruup6rnqwasxt742stdyby2xey3ymnhie", // path to dist
    "version": "1.0.0", // needed?
    "dependencies": {}, // script tags to include
    "type": "" // type definition
  }
}

Acceptance Criteria

• gateway is optional in config
• -g flag should take precedence, even if config is provided
• should use the bundleUrl in modifyIndexHtml if provided
• should use the tagName in modifiyIndexHtml if provided
• bundleUrl supports a trailing slash or no trailing slash
• bundleUrl supports a relative path to local dist (../../near-bos-webcomponent/dist)
• throws error if tagName but no bundleUrl, or bundleUrl but no tagName