Return content owner in organisation admin

[KasperBrandt]

Somehow the content owner field got removed from the admin during the last release.

[rumca]

I thought this field had been replaced by the allow edit stuff in the 2.3.6 release. If both of them are supposed to be there, can we just re-add here?

[KasperBrandt]

yup, correct.. I think I was confused with the sync_owner in the project admin, that's why I deleted it, but it should've stayed in. So we have to re-add it there indeed..

[zzgvh]

Should the content_owner be editable? My impressions was that it should be set by code that loads data through the API.

[KasperBrandt]

Yeah, I had accidentally removed it in this release because I was confused with the sync_owner in the project admin :(. But the partner team uses this field in the admin when they encounter a duplicate organisation, then they set it so that the organisation won't be overridden by data loaded through the API.

[KasperBrandt]

Merged in #562

[KasperBrandt]

Test plan

GIVEN the organisation admin
WHEN an organisation is opened
THEN the sync_owner field should be editable