feat: tenants to base structure

[danielhe4rt]

This pull request introduces multi-tenancy support to the Badge and Character modules by adding tenant_id fields and enforcing tenant-aware logic throughout models, factories, DTOs, entities, validation, routes, and tests. It also updates relevant middleware and actions to ensure all operations are scoped to the correct tenant, and modifies tests to use tenant-specific data.

Multi-tenancy support and enforcement:

• Added tenant_id as a required attribute to the Badge, Character, and PastSeason models, their factories, and their $fillable arrays to ensure all records are associated with a tenant. [1] [2] [3] [4] [5] [6]
• Updated DTOs (NewBadgeDTO) and entities (BadgeEntity) to require and serialize tenant_id, and to expect it in their static constructors. [1] [2] [3] [4] [5]
• Added validation for tenant_id in badge creation requests.

Route and middleware updates:

• Added VerifyIfHasTenantProviderMiddleware to both badge and character API route groups to enforce tenant context on all endpoints. [1] [2]

Tenant-aware logic in actions:

• Updated FindCharacterIdByUserId action to query characters by both tenant_id (from the request) and user_id, ensuring tenant isolation. [1] [2]
• Updated actions that previously referenced userId to use modelId for improved provider/character linkage. [1] [2]

Test updates for multi-tenancy:

• Refactored feature and unit tests for badges and characters to create and use tenant-specific data, including factories for tenants and passing tenant_id in payloads and headers. [1] [2] [3] [4] [5] [6] [7] [8]

Factory improvements:

• Updated factories for badges, characters, and past seasons to generate associated tenants automatically. [1] [2] [3]

These changes collectively ensure all badge and character operations are properly scoped to a tenant, laying the groundwork for robust multi-tenant support.