Feature/add a test for metadata

[THOR300]

Description

Adding a test for metadata filtering.

---

WIP failing test:

So we have metadata from vespa but then we're also querying the db for metadata. In these tests we are getting a disparity between the metadata in vespa and that in the db. Thus, the search results when using a metadata filter aren't correct. I.e. filtering for sector: Price returns results without that metadata being present.

_populate_db_families is non-deterministic as well.

vespa_families[0].hits[0].metadata -> [{'name': 'sector', 'value': 'Price'}...

>> family_and_family_metadata[0][1].value['sector'] ['Agriculture', 'Urban', 'LULUCF', 'Cross Cutting Area', 'Finance', 'Social development'...]

>>> db_family_tuple[1].value['sector'] ['Transport', 'Economy-wide', 'Disaster Risk Management (Drm)'.... Not sector: ['Price']

In theory this shouldn't happen in practice due to the db_state being from the db but is there a possibility we update metadata and before vespa is updated start getting some odd search results?

Validating this theory that there's a disparity.
Ran the following yql and proved that the vespa search results are correct against the db.
vespa query 'select * from family_document where family_import_id contains "CCLW.family.8633.0"
Validated postgres by adding a breakpoint and adding running the sql alchemy query.

---

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