feat: add backend for new user/group column

[enjeck]

Contributes to #586

This adds to the backend to support adding a new column that receives users or groups.

We expect the row values of this column to be array of objects with format {id: string, type: int}

Creating a column

Request

curl --silent \
    -X POST \
    -u admin:admin \
    -H "OCS-APIRequest: true" \
    -H "Content-Type: application/json" \
    -d '{ "baseNodeId": 1, "title": "New Column", "usergroupDefault": "[{\"id\": \"admin\", \"type\": 0}]" }' \
'http://nextcloud.local/ocs/v2.php/apps/tables/api/2/columns/usergroup?format=json' | jq

Result

{
  "ocs": {
    "meta": {
      "status": "ok",
      "statuscode": 200,
      "message": "OK"
    },
    "data": {
      "id": 7,
      "tableId": 1,
      "title": "New Column",
      "createdBy": "admin",
      "createdByDisplayName": "admin",
      "createdAt": "2024-05-13 15:25:29",
      "lastEditBy": "admin",
      "lastEditByDisplayName": "admin",
      "lastEditAt": "2024-05-13 15:25:29",
      "type": "usergroup",
      "subtype": "",
      "mandatory": false,
      "description": "",
      "numberDefault": null,
      "numberMin": null,
      "numberMax": null,
      "numberDecimals": null,
      "numberPrefix": "",
      "numberSuffix": "",
      "textDefault": null,
      "textAllowedPattern": null,
      "textMaxLength": null,
      "selectionOptions": [],
      "selectionDefault": null,
      "datetimeDefault": null,
      "usergroupDefault": [
        {
          "id": "admin",
          "type": 0,
        }
      ],
      "usergroupMultipleItems": null,
      "usergroupSelectUsers": null,
      "usergroupSelectGroups": null,
      "showUserStatus": null
    }
  }
}

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

[blizzz]

First glance looks good, have not tested myself yet

• Integration test can be extended around inserting, modifying and delete column values
• a new migration class is needed to add the new columns on existing installations (existing steps are not executed again).

[blizzz]

Will it be easier to have just one common format, with the array as above? Or would it be somehow backwards-incompatible or require too many unrelated changes elsewhere?

[enjeck]

It would be nice to have one common format. But other column types aren't arrays and I think it would take many changes to make them as such.

[blizzz]

Do you mean, if multiple users/groups are part of the search string?

[enjeck]

Yeah. But I guess we can consider this later on

[enjeck]

• Integration test can be extended around inserting, modifying and delete column values

Not sure what this entails. Do we already have this for other column types? @blizzz

[blizzz]

• Integration test can be extended around inserting, modifying and delete column values

Not sure what this entails. Do we already have this for other column types? @blizzz

I think you already covert inserting with a user.

Then there are some tests in Apiv1 on modification, e.g.

tables/tests/integration/features/APIv1.feature

Line 117 in 6793858

Scenario: Create, modify and delete rows

[blizzz]

Nitpick, otherwise the recent changes look good, have to test yet.

[blizzz]

Suggested change

	}
	}
	return null;