Escaping issue with tag values

Nessuno ha ancora preso questa issue.

This issue occurs in our case because a user has entered specific meta data fields as just `\`.
According to the Influx docs, `\` does not need to be escaped, but may be.
In our case, however, the backslash is followed with a comma, because it is at the end of the tag value, followed by another tag value, leading to messed up interpretation of the whole record.

In my opinion, the safest way to handle this is to _always_ escape backslashes.

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. Create as `List<>` with at least one tag containing just a backslash `\`
2. Write this list to InfluxDB using
`client.getWriteApiBlocking().writeMeasurements(WriteParameters.DEFAULT_WRITE_PRECISION, myList);`

__Expected behavior:__
Data would be inserted correctly.

__Actual behavior:__
Influx returns:
`HTTP status code: 400; Message: unable to parse 'metrics,account.companyName=\,account.contactCity=\ [...]`

__Specifications:__
- Client Version: 6.7.0
- InfluxDB Version: 3.7
- JDK Version: 17
- Platform: Linux/Docker/openjdk:17-alpine

Parti da client.getWriteApiBlocking().writeMeasurements(...) e riproduci il fallimento con un valore di tag contenente solo una barra rovesciata, seguito da un altro tag. Traccia come viene serializzata quella misurazione prima dell’invio della richiesta, quindi verifica che il record risultante venga accettato da InfluxDB e aggiungi la copertura per questo caso.

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