Google_workspace: prevent data gaps because of the partition filtering in gmail events

[chemamartinez]

Proposed commit message

Google Workspace:

Users were experiencing data gaps in the gmail data stream
during certain time windows (particularly affecting users in
non-UTC timezones). Events with specific time_usec values
were not being captured because the BigQuery partition
filter was too restrictive.

It has been modified the _PARTITIONTIME filter to include
a 1-day lookback.
This ensures all relevant partitions are scanned while the
precise time_usec filters guarantee only events in the
correct time range are returned.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 5d43234

cc @chemamartinez

[elastic-vault-github-plugin-prod]

Package google_workspace - 3.1.1 containing this change is available at https://epr.elastic.co/package/google_workspace/3.1.1/