Fix logbook entity_matches_only query mode

[tathamoddie]

The way that logbook data is written to the database, versus how it is read, has gotten out of sync.

The two competing optimisations are:

• Provide a logbook option entity_matches_only to optimize for single entity lookup #39555 changed the read path, introducing string-matching to pre-filter JSON blobs in the database query
• Store JSON in database in compact format #53364 changed the write path, removing whitespace from JSON formatting

No test covered this scenario.

This caused a regression in 2021.8, identified in #55724, where different query paths have inconsistent results.

Specifically, the Logbook panel displays more data than the Logbook card can.

Proposed change

Fixes #55724, which was a regression in 2021.8. This bug prevented custom log entries from displaying on the Logbook Lovelace card. They would only show on the Logbook panel, creating an inconsistent experience between the two. Now they are consistent again.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes logbook card show no automation trigger after update #55724
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[tathamoddie]

Change was implemented as per the approach suggested by @bdraco in #55724 (comment), so hopefully you could review @bdraco?