feat: Add player_configs feature and migrate user preferences

- Implemented player_configs table to store multiple player configurations per user.
- Migrated existing player settings from user_preferences to player_configs.
- Removed player-related columns from user_preferences.
- Added referral state fields to user for tracking referral rewards.
- Created migration scripts for database changes and data migration.
- Added test cases for app services and usage helpers.
- Introduced video job service interfaces and implementations.

proto/app/v1/account.proto

@@ -3,7 +3,7 @@ syntax = "proto3";
 package stream.app.v1;
 
 option go_package = "stream.api/internal/gen/proto/app/v1;appv1";
-
+import "google/protobuf/wrappers.proto"; 
 import "app/v1/common.proto";
 
 service AccountService {
@@ -11,6 +11,7 @@ service AccountService {
   rpc UpdateMe(UpdateMeRequest) returns (UpdateMeResponse);
   rpc DeleteMe(DeleteMeRequest) returns (MessageResponse);
   rpc ClearMyData(ClearMyDataRequest) returns (MessageResponse);
+  rpc GetUserById (google.protobuf.StringValue) returns (User) {}
 }
 
 service PreferencesService {
@@ -41,6 +42,7 @@ message UpdateMeRequest {
   optional string email = 2;
   optional string language = 3;
   optional string locale = 4;
+  optional string telegram_id = 5;
 }
 
 message UpdateMeResponse {