refactor: avoid evaluating Data more than once in SLOG_THROTTE macro

[SergeTupchiy]

Release version: v/e5.7.0

Summary

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|breaking)-<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

[savonarola]

We may do not call (fun() -> ... end)() before the check, e.g.:

-define(SLOG_THROTTLE(Level, Data, Meta),
    case logger:allow(Level, ?MODULE) of
        true ->
            (fun(#{msg := __Msg} = __Data) ->
                case emqx_log_throttler:allow(__Msg) of
                    true ->
                        logger:log(Level, __Data, Meta);
                    false ->
                        ?_DO_TRACE(Level, __Msg, maps:merge(__Data, Meta))
                end
            end)(Data);
        false ->
            ok
    end
).

[SergeTupchiy]

Thanks 👍 , fixed

[yanzhiemq]

TestExecution