Revise release assets for managed deployments via policies

Pre-submission Checks

• I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
• I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.

Feature description

The assets of a GitHub release do not include an ADMX template nor a macOS pList template for the distributed vendor=ownCloud product=ownCloud binaries.

Secondary: there is a second Windows MSI package with "GPO" suffix which is misleading. We usually regularly deploy the non-"GPO" MSI package with both Intune and GPO by setting proper MSI options. A compare between the two MSI packages made with ORCA shows no valuable difference between the two.

Proposed solution

Publish official ADMX templates, OMA-URIs and pList files for the ownCloud released version of ownCloud as release attached assets.

Secondary: drop the misleading ".GPO" suffix from the alternative MSI package.

Alternative solutions you considered

Secondary: drop the alternative "GPO" MSI package entirely and give better documentation on how to deploy the standard one via any Windows application deployment platform (Intune, ConfigMgr, GPO, ecc....)

Additional context

ownCloud Desktop Client 7.1.0 introduced support for configuration via policy. No policy template was provided for supported platforms (Windows, macOS). The existing alternative MSI package with "GPO" suffix become misleading as apparently related to GPO-policy (which is not true).

Start by reviewing how the 7.1.0 policy configuration support is packaged and how release assets are assembled. Compare the standard and “GPO” MSI packages with ORCA, then define the release assets for Windows and macOS; done means official ADMX, OMA-URI, and pList templates are attached and the misleading MSI suffix is addressed.