chore: fix incorrect version notation of GQL Field

[fregataa]

blocked by #2000

Change

• Correct Added/Deprecated version of Resource policy GQL schema fields
• Unify description/deprecation message to Added in {VERSION} and Deprecated since {VERSION} for consistency.
• Unify version notation to end with .(dot). e.g. "23.09.10" -> "23.09.10."
• Fix fields labeled as added in version "24.03.1" that were actually added in version "24.03.0"

Why are the versions so different?

KeyPairResourcePolicy

• max_quota_scope_size field was added by mistake in version "23.09.6", when fix: restore removed graphene fields and set them deprecated #1677 was backported (a4bad32)

UserResourcePolicy, ProjectResourcePolicy

• max_vfolder_size was actually deprecated since "23.09.2", when fix: provide deprecation msg to max_vfolder_size graphene field #1644 was backported (2a1cc67)

{Create/Modify}UserResourcePolicyInput, ProjectResourcePolicyInput

• Restore max_vfolder_size field that was removed when fix: provide deprecation msg to max_vfolder_size graphene field #1644 was backported to "23.09.2" (2a1cc67)

Warning

in 23.09, max_vfolder_count field of {User/Project}ResourcePolicy was removed in "23.09.3." by mistake and restored in "23.09.6.". So, the version the field was added in is "23.09.6."

• The commit that removed max_vfolder_count from {User/Project}ResourcePolicy: f4d6b51
• The commit that restored the field: 3d9a886

Checklist: (if applicable)

• Milestone metadata specifying the target backport version
• API server-client counterparts (e.g., manager API -> client SDK)
• Documentation
  • Contents in the docs directory
  • docstrings in public interfaces and type annotations