fix(baileys): update to 7.0.0-rc.5 and fix assertSessions signature

Problem:
- GitHub Actions failing: Expected 1 arguments, but got 2
- Local had outdated Baileys 7.0.0-rc.3 in node_modules
- assertSessions signature changed between versions

Solution:
- Fresh npm install with Baileys 7.0.0-rc.5
- Updated assertSessions to pass only jids (no force param)
- Regenerated Prisma Client after reinstall
- Updated package-lock.json for version consistency

Changes:
- assertSessions now receives 1 argument (jids only)
- Kept force param in method signature for API compatibility
- Removed @ts-expect-error directives (no longer needed)

Tested:
- ✅ Server starts successfully
- ✅ Build passes without errors
- ✅ Lint passes

src/api/integrations/channel/whatsapp/voiceCalls/useVoiceCallsBaileys.ts

@@ -71,7 +71,7 @@ export const useVoiceCallsBaileys = async (
 
   socket.on('assertSessions', async (jids, force, callback) => {
     try {
-      const response = await baileys_sock.assertSessions(jids, force as any);
+      const response = await baileys_sock.assertSessions(jids);
 
       callback(response);
 

src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts

@@ -4593,8 +4593,10 @@ export class BaileysStartupService extends ChannelStartupService {
     return response;
   }
 
-  public async baileysAssertSessions(jids: string[], force?: boolean) {
+  // eslint-disable-next-line @typescript-eslint/no-unused-vars
-    const response = await this.client.assertSessions(jids, force as any);
+  public async baileysAssertSessions(jids: string[], _force?: boolean) {
+    // Note: _force parameter kept for API compatibility but not used in Baileys 7.0.0-rc.5+
+    const response = await this.client.assertSessions(jids);
 
     return response;
   }