Add Visibility and Edit Rules to Job Orchestration Pages

[daniel-slaugh]

The functional spec requires that orchestration tasks respect workspace permission levels, allowing users with view access to observe tasks and execution status without being able to modify orchestration configuration.

General Requirements

• Orchestration pages respect workspace permission levels
• Users with view access can observe orchestration tasks and executions
• Users without edit permissions cannot modify orchestration configuration

Frontend Requirements

• Users with view-only workspace access can:
  • View orchestration tasks
  • View task schedules
  • View execution status and failure information
• Users with view-only access cannot:
  • Create new orchestration tasks
  • Edit existing tasks or schedules
  • Enable or disable tasks
  • Modify data connections or orchestration settings
• Edit controls (buttons, menus, forms) are:
  • Hidden or disabled for view-only users
  • Clearly available for editors and owners
• UI clearly communicates when a page or section is read-only

Backend Requirements

• Orchestration APIs enforce permission checks for all mutating actions
• Read-only users are restricted to non-mutating endpoints
• Unauthorized mutation attempts are rejected with appropriate errors
• Permission logic is consistent with existing workspace access rules