InfluxDB Client prevents application from exiting when batch mode is enabled

Nadie ha tomado este issue todavía.

Hi Team,

When an influxdb-java client is created and batch is enabled, it prevents the application from exiting normally due to the use of a default non-daemon thread pool. This prevents the application from shutting down in the event that the main thread exits/ crashes. Adding a shutdown hook would not help with closing the client as the JVM will only run shutdown hooks after all non-daemon thread exits. A small example would be running the following:

```java
public class App {
public static void main(String[] args) {
InfluxDB influxDB = InfluxDBFactory.connect("http://localhost:8086");
influxDB.enableBatch();
Runtime.getRuntime().addShutdownHook(new Thread(influxDB::close));
System.out.println(influxDB.ping());
}
}
```

Currently, the workaround is to explicitly specify a daemon thread factory:
```java
influxDB.enableBatch(
BatchOptions.DEFAULTS
.threadFactory(runnable -> {
Thread thread = new Thread(runnable);
thread.setDaemon(true);
return thread;
})
);
```

But I was wondering if it would be a better user experience to have this be the default behaviour so that the main application is allowed to exit normally. The rationale is that a common use case for influxdb-java is to write application metrics and usually one would not expect a metrics library to affect the main application (e.g. cause it to not exit properly).

Comienza en el punto de entrada enableBatch y en la configuración BatchOptions.DEFAULTS mostrada en el informe; después, reproduce el ciclo de vida con el ejemplo App proporcionado. Traza cómo se crea la fábrica de hilos predeterminada y verifica que la aplicación pueda salir normalmente cuando el modo batch está habilitado, conservando el comportamiento batch.

Escrito por el modelo de indexación a partir del texto del issue.