fix: rules tags key is plural

[vicenteherrera]

Catch up to Falco v0.19.0

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 examples

/area rules

/area integrations

/area tests

/area proposals

What this PR does / why we need it:

Some falco rules use the keyword "tag" instead of "tags", which is the valid one (see diff).

Which issue(s) this PR fixes:

No error message is shown on rule load, but if you try to enable or disable rules using command line switches, it wil fail to do so for those rules.

Special notes for your reviewer:

First PR, have read procedures, but may still be doing something wrong. Will try to continue sending PRs in future, so I'm willing to learn the best way to do it.

Does this PR introduce a user-facing change?:

Fix: Some rules tags were not specified correctly.

[poiana]

@vicenteherrera: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[poiana]

Welcome @vicenteherrera! It looks like this is your first PR to falcosecurity/falco 🎉

[leodido]

Hello Vicente, thanks for sending this but unfortunately the diff is empty ...

[poiana]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• 450c357 Merge pull request Digwatch compiler #1 from falcosecurity/dev
• ec84a8f Fixed use of "tag" instead of "tags" in default rules

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[poiana]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign leodido
You can assign the PR to them by writing /assign @leodido in a comment when ready.

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

Needs approval from an approver in each of these files:

• rules/OWNERS

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

[vicenteherrera]

Added missing commit. But I created the PR from my fix/tags_singlar branch, and per comments I understand I have to do it from same dev branch after rebase. Confirm and we can cancel this PR to open a new one. Sorry for the inconvenience.

[leodido]

Hey @vicenteherrera thanks for catching this 😃

Could you please remove the merge commit and sign-off your only commit?

[Kaizhe]

@vicenteherrera can you please sign you commits ? with -s in your commits.