Enable API testing

[Grotax]

This PR enables API testing by using the integrated PHP webserver.

For the test management bats is used. To query the api httpie offers more options than curl but both can be used.

[Grotax]

The API has many potential cases to test for, it will probably take some time to test all.
And on top of course we can't rely on correct documentation/implementation.

But the base setup works nicely. It even works with my instance living in a vm, reachable via http.

That is also how I developed the tests so far. VM running nextcloud and news bridged network test from local repo executing bats on host machine, replace baseurl var in the helper script.

[Grotax]

https://nextcloud.github.io/news/api/api-v1/#mark-items-of-a-folder-as-read

is broken, the reason is simple

news/lib/Controller/FolderApiController.php

Line 146 in f4aba4f

public function read(?int $folderId, int $maxItemId): void

parameter maxItemId should be newestItemId

[index] Error: OCA\News\Controller\FolderApiController::read(): Argument #2 ($maxItemId) must be of type int, null given, called in /var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php on line 217

PUT /index.php/apps/news/api/v1-2/folders/53/read

[Grotax]

Any idea how we can track the coverage in a readable format?
I assume automatic coverage reports are not possible.

I don't think I can cover every single endpoint option in this PR, especially for items it's just too much and some of the cases are difficult to test, like for a human easy but in bash you have to make arrays and compare them to each other.

[Grotax]

@SMillerDev the /items/updated api is in fact broken because when items get marked as read the lastModified timestamp is not updated. Marking as read is not enough here as this is api is supposed to return all changed items since lastModified.

Same would be for staring an item I think maybe more?

[SMillerDev]

I think that information got lost over time and this requires a new lastUpdatedSource and lastUpdatedUser division. I've been working on splitting up the feed info from the user info, but that fix will take a while.

[Grotax]

I'm not sure if I understand, every item has a last modified timestamp and a pub date.

This API checks if there is any item with a last modified bigger than the input.

Any action that modifies an item should (based on this API) update the last modified to the current timestamp.

I think all we need to do is, to adjust the dB mappers for any changing method to also update the last modified.

[SMillerDev]

I think that would also mean that it reappears on top of the feed right? Since it's then updated again?

[Grotax]

hmm I think it shouldn't as the items would be marked as read too. It's the apps responsibility to deal with that.

And it breaks syncing with the android app.

1. Sync the android app.
2. Mark items with another client as read (webapp)
3. Sync again with android update.
4. Items still not marked as read.

This timestamp is not supposed to be used for item sorting but rather a technical marker for the last change.

Alternatively we could drop the current API and built a new one.

[Grotax]

Same for marking an item as starred or unread again. The api is supposed to give the latest changes. Since the last sync.

[Grotax]

rebased on master

[Grotax]

rebase on master

[Grotax]

rebased