Add Read-Only Access Permission for Project Services

What problem will this feature address?

Summary

Add granular read-only access control for project services, allowing administrators to grant users view-only permissions for specific services without the ability to modify, start, stop, or delete them.

Problem Statement

Currently, users with service access can perform all actions (create, update, delete, start, stop, deploy) on services they have access to. There's no way to grant read-only access where users can only view service details, logs, and status without being able to make any modifications.

Describe the solution you'd like

Implement a new permission system that allows:

• Read-Only Access: Users can view service details, logs, status, and configurations
• No Modification Rights: Users cannot edit, start, stop, deploy, or delete services
• UI Restrictions: Hide/disable action buttons for read-only users
• API Protection: Block modification endpoints for read-only users

Describe alternatives you've considered

Implement service-level role inheritance where read-only users automatically get restricted access based on their organization role

Additional context

No response

Will you send a PR to implement it?

Yes

Start by mapping the existing service-access behavior across the UI and API entry points. Clarify the permission model and all read-only versus modifying actions before implementation. Done means read-only users can view the specified service information while action controls and modification endpoints consistently prevent changes.