Unit tests for madatory fields for saveClaim and claims restored

[Blue-B-code]

Description
Here I've implemented basic unit tests for the ClaimActivity class. We used Robolectric to simulate an Android environment, allowing us to access UI components and activity lifecycle methods. Mockito was used to mock dependencies like SQLHandler and Global. The tests cover data validation (isValidData()), claim saving (saveClaim()), and claim restoration (fillClaimFromRestore()).

Type of change
Chore (CI/CD)

CheckLists
Unit Tests added :

isValidData_AllValid_ReturnsTrue – PASSED ✅

isValidData_MissingHealthFacility_ReturnsFalse – PASSED ✅

isValidData_MissingClaimAdmin_WhenMandatory_ReturnsFalse – PASSED ✅

isValidData_MissingClaimCode_ReturnsFalse – PASSED ✅

isValidData_MissingInsureeNumber_ReturnsFalse – PASSED ✅

isValidData_InvalidInsureeNumber_ReturnsFalse – PASSED ✅

isValidData_MissingStartDate_ReturnsFalse – PASSED ✅

isValidData_MissingEndDate_ReturnsFalse – PASSED ✅

isValidData_MissingDiagnosis_ReturnsFalse – PASSED ✅

isValidData_MissingVisitType_ReturnsFalse – PASSED ✅

isValidData_NoItemsAndServices_ReturnsFalse – PASSED ✅

saveClaim_ValidData_CallsSqlHandlerAndReturnsTrue – PASSED ✅

saveClaim_ContentValuesContainExpectedData – PASSED ✅

fillClaimFromRestore_FillsAllFieldsCorrectly – PASSED ✅

Similarly, for certain methods (fillClaimFromRestore()), we had to temporarily increase visibility from private to protected (or use reflection) in order to test them properly.