build(deps): bump github.com/influxdata/flux

[stefanb]

bump github.com/influxdata/flux from v0.171.0 to v0.191.0

Fixes #2769

There are also newer releases that could be used: https://github.com/influxdata/flux/releases

Required checklist

• Sample config files updated (both /etc folder and NewDemoConfig methods) (influxdb and plutonium)
• openapi swagger.yml updated (if modified API) - link openapi PR
• Signed CLA (if not already signed)

Description

1-3 sentences describing the PR (or link to well written issue)

Context

Why was this added? What value does it add? What are risks/best practices?

Affected areas (if applicable):

List of user-visible changes. As a user, what would I need to see in docs?
Examples:
CLI commands, subcommands, and flags
API changes
Configuration (sample config blocks)

Severity (optional)

i.e., ("recommend to upgrade immediately", "upgrade at your leasure", etc.)

Note for reviewers:

Check the semantic commit type:

• Feat: a feature with user-visible changes
• Fix: a bug fix that we might tell a user “upgrade to get this fix for your issue”
• Chore: version bumps, internal doc (e.g. README) changes, code comment updates, code formatting fixes… must not be user facing (except dependency version changes)
• Build: build script changes, CI config changes, build tool updates
• Refactor: non-user-visible refactoring
• Check the PR title: we should be able to put this as a one-liner in the release notes

[chenrui333]

@stefanb maybe let's try including this patch and upgrading kapacitor to 1.7.1 on the homebrew side? what do you think?

[stefanb]

Not sure, the CI didn't pass here.

[chenrui333]

fix pr, #2811