Refactor GregorianCalendar constructor

[Girgias]

This really ought to be two separate static constructors but this at least makes this usable with 4 args.

[Girgias]

CI Failure is unrelated.

[nikic]

Pretty sure @kocsismate proposed something like this in the past. Same response here: Using single-signature zpp in this way is inappropriate for heavily overloaded methods like this. There is no single signature here, and pretending there is makes things worse, not better.

[kocsismate]

Pretty sure kocsismate proposed something like this in the past.

Yes, and at last I created #6754. I also think that going with a similar approach would be better in this case as well.

I plan to prepare an RFC which would deprecate the overloaded signatures where possible, but I haven't yet managed to start working on the proposal.

[Girgias]

Pretty sure @kocsismate proposed something like this in the past. Same response here: Using single-signature zpp in this way is inappropriate for heavily overloaded methods like this. There is no single signature here, and pretending there is makes things worse, not better.

Must have missed that one, my main work logic was to get rid of the zend_get_parameters_array_ex() call, and to get rid of the no 4 param variant, as it doesn't really make a lot of sense. Would this be better if it uses 2 ZPP calls, one for the Timezone/Locale version and another for the date variant? As this would still be overloaded, but at least prevent the bonkers case where you can just toss null at the end in a variant which makes utterly no sense.

[Girgias]

This is being handled by https://wiki.php.net/rfc/deprecate_functions_with_overloaded_signatures now.