Stackdriver Monitoring v4.0.0 raising errors when try to write TimeSeries

#### Environment details

- which product (packages/*): Stackdriver Monitoring v4.0.0
- OS: Ubuntu 22.04 LTS
- Node.js version: v20.8.1
- npm version:
- google-cloud-node version: 4.0.0

#### Steps to reproduce

```
const monitoring = require('@google-cloud/monitoring');

const client = new monitoring.MetricServiceClient();

const jobBillableTimeInMinutes = (job.billable_time_ms / 1000) / 60;
const metricType = `custom.googleapis.com/workflow/${resource_name}/job-duration`;

const dataPoint = {
interval: {
endTime: {
seconds: Date.now() / 1000
},
},
value: {
doubleValue: jobBillableTimeInMinutes
},
};

const timeSeriesData = {
metric: {
type: metricType,
labels: {
run_id: run_id,
job_name: job.name
},
},
resource: {
type: 'global',
labels: {
project_id: project_id,
},
},
points: [dataPoint],
};

const request = {
name: client.projectPath(project_id),
timeSeries: [timeSeriesData],
};

console.log("Sending data to Google Cloud Monitoring")
await client.createTimeSeries(request);
```

The provided code snippet throws the following error:

```
Error: 3 INVALID_ARGUMENT: One or more TimeSeries could not be written: One or more points were written more frequently than the maximum sampling period configured for the metric.: global{} timeSeries[0]:
```

The same code works with @google-cloud/monitoring: 3.0.5.

Thanks!

Parti da MetricServiceClient.createTimeSeries e riproduci la richiesta fornita con @google-cloud/monitoring 4.0.0, quindi confronta la stessa richiesta con 3.0.5. Traccia il modo in cui la richiesta TimeSeries viene validata o serializzata; il lavoro è completato quando viene identificata la causa specifica della versione e viene aggiunto un test di regressione oppure viene documentata la limitazione confermata.

Scritto dal modello di indicizzazione a partire dal testo della issue.