os-telegraf - Enable Encoding Type for InfluxDB v2 output

[igobypenn]

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• When the request is meant for an existing plugin, I've added its name to the title.

Is your feature request related to a problem? Please describe.
I'm looking use quest-db behind InfluxDb V2 line protocol.

Following https://questdb.io/docs/third-party-tools/telegraf/
quest-db doesn't support gzip encoding.

# -- OUTPUT PLUGINS -- #
[[outputs.influxdb_v2]]
# Use InfluxDB Line Protocol to write metrics to QuestDB
  urls = ["http://localhost:9000"]
# Disable gzip compression  
  content_encoding = "identity"

This configuration is generated with content_encoding = "gzip"
As a result i get the following error

E! [outputs.influxdb_v2] Failed to write metric to (will be dropped: 415 Bad request): not supported: failed to parse line protocol:errors encountered on line(s):gzip encoding is not supported - line[36466036744]```

**Describe the solution you'd like**
It would be ideal if there was 1 more configuration content_encoding 
In the UI that can be a selection (gzip, identity, zstd etc) or in the case of it being behind "advanced" configuration it could be plain text and user beware when setting the value. 


**Describe alternatives you've considered**
Alternatively i can install and generate configurations myself. Though i would have to ssh or be at console to manually manage this.
Having to be at machine to administer it is a problem and leaving ssh open is a security risk. 

An alternative solution would be allowing modifying the telegraf configuration, though this adds a validation requirement to modified configuration. As well being able to represent all that can be configured. This would go beyond the scope of just influxdb and would end up in configuration pursuit problem. 


**Additional context**
Add any other context or screenshots about the feature request here.

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.