Add es_os_refresh env var to refresh index, ensure refresh passed via kwargs

[jonhealy1]

Related Issue(s):

• ElasticSearch refresh parameter unused? #315

Description:

• Introduced the DATABASE_REFRESH environment variable to control whether database operations refresh the index immediately after changes. If set to true, changes will be immediately searchable. If set to false, changes may not be immediately visible but can improve performance for bulk operations. If set to wait_for, changes will wait for the next refresh cycle to become visible.
• Refactored CRUD methods in TransactionsClient to use the _resolve_refresh helper method for consistent and reusable handling of the refresh parameter.
• Fixed an issue where some routes were not passing the refresh parameter from kwargs to the database logic, ensuring consistent behavior across all CRUD operations.

PR Checklist:

• Code is formatted and linted (run pre-commit run --all-files)
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable
• Changes are added to the changelog

[rhysrevans3]

Looks good just one optional change 👍