Fix role schema to use camelCase naming convention

[Copilot]

The role schema used snake_case property names (role_name, created_at, updated_at, deleted_at) instead of the camelCase convention specified in the repository's README.

Changes

• Schema properties: Updated role.yaml to use camelCase (roleName, createdAt, updatedAt, deletedAt)
• Template: Updated role_template.json to match the new property names
• Generated code: Regenerated models/v1beta1/role/role.go with corrected JSON/YAML struct tags
• Imports: Restored pq and nulls package imports removed by code generator but required by other types in the file

Database column names remain snake_case via db tags; only JSON/YAML serialization uses camelCase.

// Before
RoleName string `db:"role_name" json:"role_name,omitempty" yaml:"role_name,omitempty"`
CreatedAt time.Time `db:"created_at" json:"created_at" yaml:"created_at"`

// After
RoleName string `db:"role_name" json:"roleName,omitempty" yaml:"roleName,omitempty"`
CreatedAt time.Time `db:"created_at" json:"createdAt" yaml:"createdAt"`

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.