feat: Update Accounts Module and Integration Tests

[armando-rodriguez-cko]

feat: Update Accounts Module and Integration Tests

Description:

This PR introduces updates to the Accounts module in the Checkout SDK, focusing on onboarding entities and sub-entities, response handling, and improving test cases. New helper methods and random data generation utilities have also been added for testing purposes.

---

Key Changes:

1. Accounts Module Enhancements:

   • Modified OnboardEntityRequest:
     • Made Draft and IsDraft properties nullable (bool?).
   • Updated OnboardSubEntityRequest:
     • Added JsonExtensionData for dynamic request properties.
   • Enhanced OnboardingStatus:
     • Added a new Draft enum value with [EnumMember(Value = "draft")].

2. New Helper Utilities:

   • Added utility methods for generating random data:
     • RandomString(), RandomDigits(), and RandomBusinessRegistrationNumber().
     • Created a custom HttpClient factory (CustomClientFactory) to handle schema versioning.

3. Test Updates:

   • Replaced static random data generation in integration tests with reusable helper methods.
   • Improved test coverage and response validation in AccountsClientTest and AccountsIntegrationTest.
   • Updated tests to handle random email and phone generation dynamically.
   • Modified test data to include new fields like IsDraft and structured company information.

4. Code Cleanup:

   • Removed unused imports and redundant methods in the test files.
   • Reorganized helper methods to streamline test setup and execution.

---

Impact:

• Functionality:
  • Enables more flexible handling of draft onboarding requests.
  • Simplifies test maintenance with reusable random data generators.
• Testing:
  • Increased test coverage ensures better reliability for entity and sub-entity onboarding flows.

---

Testing:

• Verified the following scenarios:
  • Successful creation of entity onboarding requests with and without the draft flag.
  • Dynamic handling of sub-entity requests using JsonExtensionData.
  • Validation of new helper methods for random data generation.

---

Notes:

• Developers should ensure the random data generators are used consistently across tests.
• Future updates may focus on additional integration scenarios and more detailed response validations.