Optimize the gcp_logging_log_entry table result or result timing by applying a timestamp filter

[ParthaI]

Describe the bug
The timestamp qual is ignored, so it's pulling down all data at once (the docs say it should work)

Steampipe version (steampipe -v)
Example: Steampipe v0.21.1

Plugin version (steampipe plugin list)
Example: v0.45.0

To reproduce
Run the following query:

select log_name, receive_timestamp,timestamp, resource_type from gcp_logging_log_entry where log_name = 'projects/hsrket-aaa/logs/diagnostic-log' and timestamp <= '2023-09-29T10:09:08+05:30';

It should only fetch the results whose log entry timestamp value is less than equal to the provided timestamp instead of fetching all the results and filtering them in the steampipe level.

Expected behavior
The table should take less time if we apply any filter for the timestamp.

Additional context
N/A

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.