Refactor to use new view based WATER models (#569)

https://eaflood.atlassian.net/browse/WATER-4057

As part of the work we have been doing on two-part tariff, we will create all our new tables in the default `public` schema.

We have also decided that when there is a legacy table that we are still going to need we will create a [View](https://www.postgresql.org/docs/current/sql-createview.html) of it in the `public` schema. This allows us to correct any issues with naming conventions, strip out unused fields, and join entities currently sat in different schemas. The first example of this approach was done in PR #531 .

We created the new views in [Create WATER schema views](#551). Then in [Create WATER schema models & helpers](#560) we added the new models and helpers that use them.

This is the final step in the process, we are refactoring any use of the legacy models to use the new ones and deleting all the legacy-based code.

app/controllers/billing-accounts.controller.js

@@ -20,7 +20,7 @@ async function changeAddress (request, h) {
   const { address, agentCompany, contact } = validatedData.value
 
   const result = await ChangeAddressService.go(
-    request.params.invoiceAccountId,
+    request.params.billingAccountId,
     address,
     agentCompany,
     contact