refactor scopes for instance services

[aditya-mitra]

Summary

🤖 Generated by Copilot at c491093

This pull request adds scope-based authorization to various services related to instances, such as instance-active, instance-attendance, instance, instanceserver-load, and instanceserver-provision. It introduces the instance:read and instance:write scopes to control the access to the instance data and the server load and provisioning data. It also updates the queries and hooks to use the new scope types.

References

refs #9161

Explanation

🤖 Generated by Copilot at c491093

• Restrict access to instance-related services based on scopes (link, link, link, link, link, link, link, link, link, link)
• Require instance:read scope for external requests to find method of instance-active, instance-attendance, and instance services (link, link, link)
• Require instance:write scope for external requests to create, patch, and remove methods of instance-attendance service (link, link)
• Require instance:write scope for external requests to create, update, patch, and remove methods of instance service (link)
• Require instance:write scope for external requests to patch method of instanceserver-load and instanceserver-provision services (link, link)
• Use iff and isProvider functions to conditionally apply scope verification hooks based on the provider of the request (link)
• Change the query for adminScopes variable in addLocationSearchToQuery hook to match instance:read type instead of admin:admin type (link)
• Remove unnecessary scope verification hooks from all hooks of instanceserver-load and instanceserver-provision services (link, link)

🤖 Generated by Copilot at c491093

Sing, O Muse, of the mighty pull request
That changed the scopes of the instance service
And added security to many a hook
To guard the data of the cloud from harm.

QA Steps

List any additional steps required to QA the changes of this PR, as well as any supplemental images or videos.

Checklist

• If this PR is still a WIP, convert to a draft
• When this PR is ready, mark it as "Ready for review"
• ensure all checks pass
• Changes have been manually QA'd
• Changes reviewed by at least 2 approved reviewers