The AcceptSpoke and RejectSpoke API methods and the network-connectivity spokes accept and network-connectivity spokes reject CLI commands have the following usability issue

## Issue The [AcceptSpoke](https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/vpc-review-proposed-spokes#accept%5Fa%5Fspoke%5Fproposal) and [RejectSpoke](https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/vpc-review-proposed-spokes#reject-a-spoke-proposal) API methods and the `network-connectivity spokes accept` and `network-connectivity spokes reject` CLI commands have the following usability issue: * As the user, if you do not have the `networkconnectivity.operations.get` IAM permission in a spoke project, you cannot [get the status](https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest/v1/projects.locations.operations/get) of a long-running operation for that spoke. The issue is being worked on. The workaround is that the spoke administrator can grant the required permissions to the appropriate hub administrator. For information about granting permissions, see [Give access](https://cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/vpc-give-access).