Watchkeeper post to razeedash fails when URL rewriting is used

[thecheryl]

Describe the bug
When using URL rewriting to route requests to Razee, watchkeeper fails to post to razeedash because the API base path is hardcoded to /api/v2 here https://github.com/razee-io/Razeedash-api/blob/1fe88efc21a2ba9e46aa8938fa9604828c0b7358/app/routes/install/index.js#L30.

In the watchkeeper logs we see “POST heartbeat to razeedash failed” and this is because it’s trying to post to https://<host>/api/v2/clusters/... instead of the route we are using for razeedash-api which is https://<host>/api/collector/v2/clusters/....

To Reproduce
Using Istio, we have a rewrite rule set up like this:

- match:
    - uri:
        prefix: /api/collector
    rewrite:
      uri: /api

So everything routed to https:///api/collector gets rerouted to https:///api

Expected behavior
We would like the API base path in https://github.com/razee-io/Razeedash-api/blob/1fe88efc21a2ba9e46aa8938fa9604828c0b7358/app/routes/install/index.js#L30 and everywhere else in the code to be configurable.

[mckaymic]

@thecheryl I'm going to put this in the backlog for now. This request can also be fixed with an ingress configuration.