BrowserCallable-aware package handling in Flow

[mshabarov]

Describe your motivation

Follow-up for #20289.

When Hilla's browser callable aka endpoints are present in a project, the Hilla TS endpoints generator packages have to be added.
Flow should know whether to add them during build time based on presence BrowserCallable / Endpoint annotated classes in a project.

Describe the solution you'd like

These annotations are Hilla owned, so there should be a new API to pass this flag from Hilla.
It could be a method like hasBrowserCallables() in EndpointGeneratorTaskFactory interface that calls BrowserCallableFinder internally or Hilla can make BrowserCallableFinder discoverable through lookup for Flow.

We have to change the ordering of node tasks in Flow from

TaskUpdatePackages.class,
TaskRunNpmInstall.class,
TaskGenerateOpenAPI.class,
TaskGenerateEndpoint.class,

to

TaskGenerateOpenAPI.class,
TaskUpdatePackages.class,
TaskRunNpmInstall.class,
TaskGenerateEndpoint.class,

(discover endpoints -> add generators if needed -> npm install -> generate endpoints if needed)

Describe alternatives you've considered

Revert the #20289 and document the workaround.

Additional context

Target version - 24.7

[tepi]

Reverted due to the changes causing test failures in Hilla. For now, the workaround of adding a dummy view should be used, and the issue will be revisited in the future.