fix: remove deprecated Instagram scopes that Meta no longer accepts

Meta's new use-case based permission system no longer accepts
`instagram_manage_comments` and `instagram_manage_insights` as valid
OAuth scopes, even though these permissions appear in their developer console.

Attempting to use the newer `instagram_business_manage_*` names also fails.

This removes the problematic scopes to allow Instagram connection to work.
Users will lose commenting and insights features until Meta/Postiz figure
out the correct scope names for the new permission system.

Tested: Instagram (Facebook Business) connection now works.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: Avry

libraries/nestjs-libraries/src/integrations/social/instagram.provider.ts

@@ -30,8 +30,6 @@ export class InstagramProvider
     'pages_read_engagement',
     'business_management',
     'instagram_content_publish',
-    'instagram_manage_comments',
-    'instagram_manage_insights',
   ];
   override maxConcurrentJob = 200;
   editor = 'normal' as const;