Handle calling the property service in transaction better

[jhrozek]

Summary

• Pass a transaction handle to RetrieveAllProperties and RetrieveAllPropertiesForEntity - These interface methods wouldn't take transaction into account.
• Call an explicit commit in ListEvaluationHistory handler - We refresh the properties in the historical evaluation endpoint (which btw should just be temporary to convert from the old tables to the new general tables) and missed the fact that the handler starts a transaction and then always rolls back - that was probably a way to keep consistence. This means that the transactions that refresh properties are rolled back and on next call fetched again. This hurts performance quite a bit on repeated listHistory calls.

Fixes: #4393

Change Type

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

by calling the list history endpoint with expired entities

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[coveralls]

coverage: 53.274% (-0.009%) from 53.283%
when pulling a9a09de on jhrozek:pass_tx_to_prop_svc
into bcdd94e on stacklok:main.

[jhrozek]

smoke tests succeeded locally - I'll merge once we stabilize our infra smoke tests

[jhrozek]

rebased on current main

[jhrozek]

and a lint fix