Include RichObject for forms

[jotoeri]

Includes the form-richObject for Events/Activities. Ref. nextcloud/forms#789

@nickvergessen I'm not completely sure, what to set as since. I now set 21.0.1 as this seems to me like the 'next' release. However, this PR is now on master (so 22.0.0?), Forms still supports 19, so 19.0.10 with a backport? 🙈

[nickvergessen]

Well this is "public api", it mostly means 22, we so far never backported stuff on it. But then again new things don't break old consumers of the API so should be okay to backport.

[nickvergessen]

Approving apart of the since version which we have to clarify

[nickvergessen]

So we also have 11.0.2 on "call" so I guess we can backport this as well.

[jotoeri]

So i set this to 19.0.10 then...?

[jotoeri]

@nickvergessen Is 19 ok? Or better 20? Unfortunately it depends a bit on this question, when we can start using it. 🙈

[nickvergessen]

If it's up to me I would only put it in 21
you can check it manually in your app by validating a "forms-form" parameter and when valid use it, if not use highlight fallback

[jotoeri]

Ah, that's sad. But ok. 🤷‍♂️ It's 21 again and i'll have a look onto this validation. 😉

[jotoeri]

/backport to stable21

[skjnldsv]

🐘

[rullzer]

Probably wildly off-topic. But is there a reason we need all this in core... wouldn't it be enough if apps can provide such things themselves?

[nickvergessen]

The idea was to have "stable api versioning" with the nextcloud version so if a moible client supports a given version it also doesn't break with any of those parameters but handles them gracefully.

[rullzer]

@nickvergessen you ok now to merge this?

[welcome]

Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22