feat(api): Apply rate limit decorators to api controllers and methods

[rifont]

What change does this PR introduce?

• Apply rate limit guard category and cost decorators to api controllers and methods. All non decorated endpoints have a Global category and Single cost applied by default, per feat(api): Add API rate limiting NestJS guard #4910
• Categories - Controllers - Endpoints [Cost]:
  • Trigger:
    • /events
      • /events/trigger - [Bulk]
      • /events/broadcast - [Bulk]
  • Configuration
    • /subscribers
      • /subscribers/bulk - [Bulk]
    • /tenants
    • /topics
  • Global
    • /changes
      • /changes/bulk/apply - [Bulk]
    • /invites
      • /invites/bulk - [Bulk]

Why was this change needed?

In order to provide a fair service to all clients, some API resources must have a differing category and cost applied given that underlying resource consumption can vary. This change colocates resources and methods whose category falls into a similar infrastructure bucket, and applies bulk cost to bulk endpoints which place a higher load on infrastructure.

Other information (Screenshots)

N/A

[linear]

NV-3062 🏎️ API Resource Protection

What?

• Attach the rate limiting guard to the relevant controllers - UseGuards(RateLimitGuard(CategoryTypeEnum.<ENUM>))
• Attach the guard to the App-level - UseGuards(RateLimitGuard(CategoryTypeEnum.Global))

Why? (Context)

In order to rate limit access to specific resources in the service, we must apply the custom Rate Limiting controller to specific resources to allocate access to them into a specific bucket.

Definition of Done

• All endpoints listed in a specific resource category have the rate limiting controller applied