Backport: Resolve project parent before other fields in updateProject - #7367

…cyTrack#7262)

* Resolve project parent before other fields in updateProject

getObjectByUuid, used to resolve the new parent, triggers a query. Any
JDO query flushes dirty state first, so if the parent block ran after
setClassifier but before setCollectionLogic cleared it, converting a
collection project back to a regular one while also changing its
parent flushed a row with both fields set, violating
PROJECT_COLLECTION_CLASSIFIER_check and surfacing as an uncaught 500.

The same hazard is already handled a few lines below for the
collection tag, which is resolved before collectionLogic is set for
exactly this reason. Moving parent resolution to the top of the
method, before any field is touched, applies the same fix: the query
now runs while the object is still clean, so nothing is flushed early.

Added a test reproducing the reported request shape: converting a
collection project back to a regular one, with a classifier and a
parent in the same request. Reverting the fix reproduces the original
500.

hasActiveChild and getLatestProjectVersion also run queries between
setClassifier and setCollectionLogic, for the isActive and isLatest
branches respectively. Same hazard, not exercised by the reported
case or by the added test, and not changed here to keep this fix
scoped to what was reported and verified.

Signed-off-by: adityaanikam <adityanikam9502@gmail.com>

* Apply Spotless formatting to ProjectResourceTest

The Lint Java check failed on the test added in the previous commit:
one assertion was longer than palantir-java-format allows. This only
rewraps that line.

Signed-off-by: adityaanikam <adityanikam9502@gmail.com>

---------

Signed-off-by: adityaanikam <adityanikam9502@gmail.com>
(cherry picked from commit 8f399b6)
Signed-off-by: nscuro <nscuro@protonmail.com>