Enable Non-Owners to Replace R/Shiny Deployments

Background: After making changes to an R/Shiny dashboard (and promoting the updated asset to a deployment space), it is preferable to "replace the asset" of an existing deployment rather than create an entirely new one (and delete the old one).

Issue: Users who did not originally deploy a dashboard are no longer able to use the "replace assets" button to update an existing deployment (in 4.6.6). For example, if I create a deployment from a promoted asset and someone else wants to update it, they receive the following error message in the deployment space.

Steps to reproduce:

1. Deploy an asset in a CP4D deployment space (promoted from within a project using Deprecated Git).

2. Promote a separate asset to the same deployment space.

3. Have a different user try to replace the asset for the currently deployed dashboard.

Impact: It is more difficult to collaborate on dashboards if a single user has to be in charge of the final deployment/replace asset step.

Workaround: Delete the previous deployment and create a new deployment using the same "Serving name" (so that the URL does not change). In CP4D 4.8.4, users with the admin role in a deployment space will be able to replace assets for other users' R/Shiny deployments in the deployment space. However, I do not feel comfortable giving one of those users admin access in order to replace R/Shiny assets.

Proposed Solution: Bring back previously existing functionality (i.e., give users with the editor role in a deployment space the ability to replace assets for other users' R/Shiny deployments).