fix(asana): remove MySQL-specific gorm type tags for PostgreSQL compatibility

Remove explicit `gorm:"type:double"` and `gorm:"type:int unsigned"` tags
from the Asana task migration struct. PostgreSQL does not have a `double`
type (it uses `double precision`) and does not support `UNSIGNED` integer
qualifiers. Without explicit tags, GORM infers the correct column type
per dialect automatically.

Follows the same pattern as #8779 which fixed equivalent issues in the
copilot plugin.

closes #8835

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: JAORMX

backend/plugins/asana/models/migrationscripts/20250212_add_task_transformation_fields.go

@@ -32,9 +32,9 @@ type asanaTask20250212 struct {
 	StdType         string   `gorm:"type:varchar(255)"`
 	StdStatus       string   `gorm:"type:varchar(255)"`
 	Priority        string   `gorm:"type:varchar(255)"`
-	StoryPoint      *float64 `gorm:"type:double"`
+	StoryPoint      *float64
 	Severity        string   `gorm:"type:varchar(255)"`
-	LeadTimeMinutes *uint    `gorm:"type:int unsigned"`
+	LeadTimeMinutes *uint
 }
 
 func (asanaTask20250212) TableName() string {