We still require a single user to be an owner. But you can set a group to have CAN_MANAGE which unblocks most of the necessary updates. It is released in all Premium workspaces that have Jobs ACLs. The official OWNER is whose identity is used to create the cluster and read the notebook. So we need an individual for that. But managers can change anything about the Job -- notebooks, configs, permissions, etc.

https://docs.databricks.com/security/access-control/jobs-acl.html#job-permissions