fix: resolve circular import errors in TypeORM entities

- Use string-based @OneToMany relations in parent entities (wallet, ticket, service-plan)
  to break circular import chains that confused VS Code TS language server
- Add .vscode/settings.json to suppress Tailwind CSS @tailwindcss unknownAtRules warnings
- Reorder imports in child entities for consistency

backend/src/tickets/entities/ticket-message.entity.ts

@@ -6,9 +6,9 @@ import {
   ManyToOne,
   JoinColumn,
 } from 'typeorm';
-import { Ticket } from './ticket.entity';
 import { User } from '../../users/entities/user.entity';
 import { UserRole } from '../../common/enums';
+import { Ticket } from './ticket.entity';
 
 @Entity('ticket_messages')
 export class TicketMessage {

backend/src/tickets/entities/ticket.entity.ts

@@ -10,7 +10,6 @@ import {
 } from 'typeorm';
 import { TicketDepartment, TicketStatus, TicketPriority } from '../../common/enums';
 import { User } from '../../users/entities/user.entity';
-import { TicketMessage } from './ticket-message.entity';
 
 @Entity('tickets')
 export class Ticket {
@@ -36,8 +35,8 @@ export class Ticket {
   @JoinColumn({ name: 'userId' })
   user: User;
 
-  @OneToMany(() => TicketMessage, (msg) => msg.ticket, { cascade: true })
-  messages: TicketMessage[];
+  @OneToMany('TicketMessage', 'ticket', { cascade: true })
+  messages: any[];
 
   @CreateDateColumn()
   createdAt: Date;