Remove seconds for minimumDate and maximumDate that affect comparison

[yfyau]

This pull request resolves the issue where onDateChange is not triggered upon bouncing back to a valid date.
Upon reviewing the Android-side code, I identified a date comparison bug. The bug arises because selectedDate has its seconds trimmed using getFormatPattern(), while minimumDate does not undergo the same process. Consequently, a scenario like 01-02-2024 15:30:00 < 01-02-2024 15:30:45 occurs, causing the following condition to always evaluate as false and preventing the code from reaching the Emitter.onDateChange line.

react-native-date-picker/android/src/main/java/com/henninghall/date_picker/ui/WheelChangeListenerImpl.java

Lines 50 to 54 in 1ab9152

	Calendar minDate = state.getMinimumDate();
	if (minDate != null && selectedDate.before(minDate)) {
	uiManager.animateToDate(minDate);
	return;
	}

[henninghall]

Thanks for the PR! Since this is an issue only on android, I moved the code to the android specific component. Also added a test for this.