Ftp max tx comment in suricata.yaml and rule for ftp.too_many_transactions event

[alinse-pltzr]

Background:

• max tx for ftp is documented here
• its also implemented in the ftp parser (see https://github.com/OISF/suricata/blob/main/rust/src/ftp/ftp.rs#L204 ) and a default of 1024 is configured (see: https://github.com/OISF/suricata/blob/main/src/app-layer-ftp.c#L53 )
• a rule which generates a ftp.too_many_transactions event is currently missing
• there is also missing a comment in suricata.yaml indicating the config option exists whereas for other protocols with a configurable max-tx there is a comment in suricata.yaml

Describe changes:

• added max-tx to ftp section in app layer of suricata.yaml.in
• added rule to generate 'ftp.too_many_transactions` event

SV_BRANCH: OISF/suricata-verify#3037

[jufajardini]

Thanks for your contribution :)

Could you please edit your PR description to add an SV branch in the format as seen here: #15209 (otherwise, the CI checks won't pick it up).

Also, please have a look at our guidelines for commit messages, and adjust them accordingly :)

https://docs.suricata.io/en/latest/devguide/contributing/code-submission-process.html#commits

[jlucovsky]

These changes are fine; however, the FTP parser isn't generating the "too many transactions" event. I'll create a ticket for that: https://redmine.openinfosecfoundation.org/issues/8489

[catenacyber]

So, this is fine, but is is missing the ftp-parser generating the event so that the rule can trigger

[jlucovsky]

Do you mind if I cherry-pick your commits into a PR that also raises the event?

[alinse-pltzr]

Do you mind if I cherry-pick your commits into a PR that also raises the event?

No, I m ok with that :) thanks for adding the event

[catenacyber]

Superseded by #15292