APIv3 - Fix regression in handling chained calls with sequential

[seamuslee001]

…sage

Overview

This fixes a bug caused by the recent security release which forced any chained api calls to be outputted in sequential even if not requested.

Before

if Sequential was missing from the array or included the result was forced into a sequential array in the chain

After

sequential is correctly managed

@KarinG @demeritcowboy can you test this on your webform stuff?

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[demeritcowboy]

can you test this on your webform stuff?

Yes! As of a few weeks ago there's this handy new option to test against a core PR:

[demeritcowboy]

Locally just doing a similar cv call to what uscounties does with this PR applied gives the right output.

Should be against 5.50 though.

[seamuslee001]

@demeritcowboy see #23673 for the 5.50 version, this one is the analogous of the RC PR

[totten]

FWIW, there is some test coverage around the recent chaining fix in CRM_Utils_RestTest. It would be good to add some coverage for this use-case (and RestTest should be a decent template).

However, considering that this is a very recent regression, that won't block merging the present PR.