New OCS endpoint to list text processing tasks

[julien-nc]

refs nextcloud/text#4613

This adds a /tasks/app/{appId} endpoint to get a list of tasks for the current user, for a specific app and optionally with a specific identifier.

While playing with the API, I discovered that it's impossible to schedule a task while not being authenticated (mostly because of a NotNull Db constraint on the user_id column). But all the endpoints are public. Maybe we should sort this out first.

• Do we want to allow non-authenticated users to schedule a job?
  • If so, do we want to be able to list all tasks that were scheduled publicly?
  • If not, should we require auth for all those endpoint?
• Are we fine with a user only being able to list his/her own tasks?
  • This would mean publicly scheduled tasks can be listed by any other non-authenticated user. Are we fine with that?

TODO

• add proper index(es)
• allow authenticated users to list all their tasks by app (and optionally by identifier)

[julien-nc]

What's been done:

• Convert annotations to Php method attributes
• Rename languageModelManager to textProcessingManager in the API controller
• Add endpoint for authenticated users to list their tasks by appId (and optionally by identifier)
• Add manager and mapper methods to:
  • get a task by user id and task id
  • get a list of task by user id and app id (and optionally with a specific identifier)
• Allow null user_id in textprocessing_tasks so tasks can be scheduled anonymously
• Add user_id, app_id, identifier index to textprocessing_tasks

@juliushaertl So it's only possible to list tasks by app while being authenticated. This is to prevent anonymous users to be able to list all tasks that were created by other anonymous users. Any problem with that in the Text integration?

[juliushaertl]

So it's only possible to list tasks by app while being authenticated. This is to prevent anonymous users to be able to list all tasks that were created by other anonymous users. Any problem with that in the Text integration?

Fine with me as the MVP. I'd then limit the text integration to logged in users only for now.

[julien-nc]

Rebased on master, bumped server version to 28.0.0.2 to trigger the migration step. All good IMO.

[juliushaertl]

Seems good, tested and works for my use case. 👍

Psalm is still not happy though.

[marcelklehr]

✨

please make sure to fix psalm, though

[juliushaertl]

Failing drone acceptance test is unrelated, also there on master https://drone.nextcloud.com/nextcloud/server/38240/57/4

[juliushaertl]

@julien-nc @marcelklehr Is there already documentation for the text processing to extend on?

[juliushaertl]

Not triggering the backport yet, but I have it on my list of requirements for 27.1

[marcelklehr]

@juliushaertl

Yes, text processing docs have already been merged, should be easy to extend for this :)

I've also created #39738 :)