added brakets to three macros to make them less ambiguous

[ldegio]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:

rules that mix and operators with or operators in a flat way (i.e. without brackets to explicitly separate them) have a couple of challenges:

• they are ambiguous to read, because the falco filter interpreter doesn't currently implement operator precedence
• they are not parsed correctly, because the filter interpreter sometimes is not capable of fully evaluating them

It turns out that there are only 3 macros in the whole ruleset that mix and and or operators without brakets. This PR modifies them by adding the required brakets.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

rule(macro inbound_outbound): add brackets to disambiguate operator precedence
rule(macro redis_writing_conf): add brackets to disambiguate operator precedence
rule(macro run_by_foreman): add brackets to disambiguate operator precedence

[fntlnz]

Changes LGTM

[poiana]

LGTM label has been added.

Git tree hash: 86e77e76a89f7194b59d483965177c314a602031

[leodido]

Thanks for this Loris! 🎉

I've updated the release-note block lines to make them match the guidelines.

Would you please just sign-off your commit and force push it? Thanks again 😃

[leogr]

LGTM

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fntlnz, leodido, leogr

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• rules/OWNERS [fntlnz,leodido,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment