Include rate limit state in existing per-request log messages
After the result object is enriched with rate limit state (https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/work_items/28785), include rate limit information in the existing per-request structured log entries rather than emitting separate log messages.
Fields to add to existing request logs: matched rule name, action, exceeded, and rate limit state (remaining, limit, reset_time) from the enriched result.
This avoids doubling log volume by not emitting separate rate limit log lines.
Context: https://gitlab.com/gitlab-org/ruby/gems/labkit-ruby/-/merge_requests/272#note_3294183874
Depends on: https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/work_items/28785
Parent epic: https://gitlab.com/groups/gitlab-com/gl-infra/-/work_items/2021
issue