Fix read model queries when selecting deeply-nested arrays (local provider)

[MarcAstr0]

Description

This PR is related to #1552. It fixes the same issue but for the local provider. It changes the approach to selecting fields when querying read models in the local provider. Instead of passing projections to NeDB, the full object will be retrieved, and the fields indicated in the selection will be filtered in.

Changes

• Modifies read-model-registry.ts to change how read models are queries.
• Test added to read-model-registry.test.ts for querying a complex read model.

Checks

• Project Builds
• Project passes tests and checks
• Updated documentation accordingly

[what-the-diff]

PR Summary

• Change Log File Addition
  A new JSON file that logs changes has been added. This file, titled fix_nested_arrays_2024-09-27-19-40.json, details a patch that addresses handling of deeply-nested arrays in Read Model queries - complex database requests.

• Updated Software Dependencies
  We've updated the versions of several software packages under the name @boostercloud in a file named pnpm-lock.yaml. These versions have changed from ^2.18.1 to ^2.18.2, promising better functionality and security.

• Read Model Registry Refactoring
  Several important changes have been made to the Read Model Registry. We've removed local functionality that handled array fields, making the system simpler and more efficient. New code has been introduced - the filterFields method - that helps in filtering the returned search results based on specific criteria.

• Testing Enhancements
  A new test case has been added to the read-model-registry.test.ts file, designed to ensure that only projected (expected) fields are returned for complex Read Models. This is done to ensure that our updated query method is functioning as intended.

[MarcAstr0]

/integration sha=c4a9e04

[github-actions]

⌛ Integration tests are running...

Check their status here 👈

[github-actions]

✅ Integration tests have finished successfully!

[davidverdu]

LGTM