Adding in local full stack deployment changes.

[THOR300]

Description

This pull request is a bug fix for a failing local deployment of the frontend and backend.

• Change the vespa url that the backend uses. Port 19071 is the config endpoint whereas 8080 is the content endpoint, see the documentation here.

The port 8080 is published to make the search and feed interfaces accessible from outside the docker container, 19071 is the config server endpoint. Only one docker container named vespa can run at a time so change the name if needed. See Docker containers for more insights.

• Creates a local certificates directory with empty cert and key. The vespa code just expects us to be passing these in or an api key.
• Adds documentation and some initial draft code for spinning up ones local environment to test the frontend and backend stack. This includes details of dumping and loading data from vespa.

Note: We're not actually passing in the vespa url from the .env into the docker-compose is there a reason for this, do we want to change this?

Proposed version

Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.

• Skip auto-tagging
• Patch
• Minor version
• Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.

Notes:

• If none of these options are selected, auto-tagging will fail
• Where multiple options are selected, the most senior option ticked will be
  used -- e.g. Major > Minor > Patch
• If you are selecting the version in the list above using the textbox, make
  sure your selected option is marked [x] with no spaces in between the
  brackets and the x

Type of change

Please select the option(s) below that are most relevant:

• Bug fix
• New feature
• Breaking change
• GitHub workflow update
• Documentation update
• Refactor legacy code
• Dependency update

How Has This Been Tested?

Please describe the tests that you added to verify your changes.

Reviewer Checklist

• DB_CLIENT DEPENDENCY IS ON THE LATEST VERSION
• The PR represents a single feature (small driveby fixes are also ok)
• The PR includes tests that are sufficient for the level of risk
• The code is sufficiently commented, particularly in hard-to-understand areas
• Any required documentation updates have been made
• Any TODOs added are captured in future tickets
• No FIXMEs remain

[linear]

PLA-219 Test concept filtering locally using local vespa instance, postgres instance, backend and frontend

[katybaulch]

amazing ⭐ ⭐