Convert range-web and range-api to mono-repo

**Describe the task**
Rather than have separate repositories, we would have one to encompass both web and API. This is to support #673, reason being is that with a PR based deployment, you get a PR based URL (https://test_app.ca/PR22), which is great, however, if the API is in a separate repo, and it's endpoints (which the web site needs) are also PR specific (and would have their own set of numbers, like (https://test_api.ca/PR22 where 22 is a totally different PR), there's no simple mechanism to point the right web deployment to the right API deployment, other than manually deciding and subsequently setting that in the web deployment.

In the mono-repo approach, a PR with changes to web or API gets its own API deployment, and web, all with PR specific endpoints and URLS, and no manual linking is required to get the user testing.

**Acceptance Criteria**
- [ ] History is preserved

Start by reviewing the range-web and range-api repository layouts and the deployment approach described for issue #673. Define how both applications will coexist in one repository while preserving history and producing matching PR-specific web and API URLs. Done means the repositories are combined, history remains available, and deployment no longer requires manually matching separate PR numbers.

Written by the indexing model from the issue text.