Remove minLength validation for the secondEmail attribute from the OpenAPI spec. (#520)

fix: Remove minLength constraint from UserProfile.secondEmail to allow empty strings

The Okta API returns empty strings ("") for users without a secondary email,
but the secondEmail field had a minLength: 5 constraint that caused Pydantic
validation to fail during deserialization of valid API responses.

Changes:
- openapi/api.yaml: Remove minLength: 5 from UserProfile.secondEmail
- okta/models/user_profile.py: Remove min_length=5 from second_email field

The upstream OpenAPI spec fix was approved and merged.
This aligns the SDK with the corrected spec.

Testing:
Verified on live org by fetching a user with secondEmail set to "" (empty string).
The user deserializes successfully without validation errors.

Fixes: OKTA-1146937
Refs: #477, #481

Author: BinoyOza-okta

okta/models/user_profile.py

@@ -188,9 +188,7 @@ class UserProfile(BaseModel):
         "https://datatracker.ietf.org/doc/html/rfc1808).",
         alias="profileUrl",
     )
-    second_email: Optional[
-        Annotated[str, Field(min_length=5, strict=True, max_length=100)]
-    ] = Field(
+    second_email: Optional[Annotated[str, Field(strict=True, max_length=100)]] = Field(
         default=None,
         description="The secondary email address of the user typically used for account recovery. For validation, "
         "see [RFC 5322 Section 3.2.3](https://datatracker.ietf.org/doc/html/rfc5322#section-3.2.3).",

openapi/api.yaml

@@ -82223,7 +82223,6 @@ components:
           type: string
           format: email
           description: The secondary email address of the user typically used for account recovery. For validation, see [RFC 5322 Section 3.2.3](https://datatracker.ietf.org/doc/html/rfc5322#section-3.2.3).
-          minLength: 5
           maxLength: 100
           nullable: true
         state: