fix: keep builtin_console actions not complain args

[zhongwencool]

Fixes https://emqx.atlassian.net/browse/EMQX-10992
Don't need changelog, v5.2.0 is ok.

There was previously a bug allowing invalid fields:

The API for creation/update did not validate the args field, and rules were being created with default args.

The configuration file also did not validate the args field.

Now after being fixed, validation has been enabled:

This causes any rules/configurations saved earlier with invalid args to no longer work.

We fixed the validate here:
78c5a77#diff-5799d1ec01ad3359596ab22f7781d2b34e8f7909194bb0785f7d1dbe677a0d88L202-L208

compatibility with actions. args

rule_engine {
  ignore_sys_message = true
  jq_function_default_timeout = 10s
  rules {
    rule_u54w {
      actions = [
        {
          args {}
          function = console
        }
      ]
      description = ""
      enable = true
      metadata {created_at = 1694748634418}
      name = ""
      sql = "SELECT\n  *\nFROM\n  \"t/#\" \n  WHERE payload.message.header.function='pmMsgReq'"
    }
  }
}

And

Summary

🤖 Generated by Copilot at d72348c

Fix a validation bug for the builtin_action_console rule action and update the emqx_rule_engine version. The bug caused the console action to fail validation when saving the rule config due to an invalid args field. The fix removes the args field from the console action config and adds it to the schema as a deprecated and ignored field. The version update reflects the bug fix and other changes in the application.

PR Checklist

Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:

• Added tests for the changes
• Added property-based tests for code which performs user input validation
• Changed lines covered in coverage report
• Change log has been added to changes/(ce|ee)/(feat|perf|fix)-<PR-id>.en.md files
• For internal contributor: there is a jira ticket to track this change
• Created PR to emqx-docs if documentation update is required, or link to a follow-up jira ticket
• Schema changes are backward compatible

Checklist for CI (.github/workflows) changes

• If changed package build workflow, pass this action (manual trigger)
• Change log has been added to changes/ dir for user-facing artifacts update

[kjellwinblad]

Looks ok to me but would be great with a test case to ensure that we don't break this in the future!

[thalesmg]

Nit: maybe this could have a test case?

[thalesmg]

Q: is this change intended for this PR? Seems unrelated. 🤔

[zhongwencool]

Yes, It's not related, I just fix this incidentally, because keepalive api is hidden for swagger.