feat: add independent scale permission

[leebrouse]

What this PR does / Why we need it:

This PR introduces an independent permission for replica scaling ("调整副本") to decouple scale operations from generic environment management permissions.

Previously, scale APIs were controlled by broader permissions (e.g. manage pods or rollback in some SAE paths), which made authorization boundaries unclear. This change makes scale authorization explicit and consistent across interfaces.

What is changed and how it works?

• Added new project-level permission verbs:
  • scale_environment
  • scale_production_environment
• Added corresponding auth fields in project permission aggregation:
  • Env.Scale
  • ProductionEnv.Scale
• Updated permission mapping logic in user auth service:
  • scale_environment -> Env.Scale = true
  • scale_production_environment -> ProductionEnv.Scale = true
• Updated collaboration mode action constants for scale:
  • EnvActionScale
  • ProductionEnvActionScale
• Switched scale-related authorization checks in Aslan handlers from old permissions to the new scale permission:
  • environment service scale API (scaleNew)
  • OpenAPI scale API
  • SAE rescale API
• Synchronized action initialization scripts for both MySQL and DM:
  • added "调整副本" actions for Environment and ProductionEnvironment in:
    • action_initialization.sql
    • dm_action_initialization.sql

Does this PR introduce a user-facing change?

• API change
• database schema change
• upgrade assistant change
• change in non-functional attributes such as efficiency or availability
• fix of a previous issue

---

This change is 

[PetrusZ]

另外还需要增加一下ua的代码

[PetrusZ]

副本扩展?

[PetrusZ]

用户有ManagePods权限时，才能给他添加Scale权限。协作模式同理。

[PetrusZ]

另外最好能优化一下ua的代码，现在太冗长了