Include rate limit state in existing per-request log messages

After the result object is enriched with rate limit state (#28785 (closed)), 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: gitlab-org/ruby/gems/labkit-ruby!272 (comment 3294183874) Depends on: #28785 (closed) Parent epic: gl-infra#2021