Don't wait for project authorization sidekiq jobs when creating projects

What does this MR do?

When creating a project, ensures the creator's authorizations are refreshed inline, demoting other affected users to asynchronous refresh

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

We only wait so the requesting user can interact with their newly-created project immediately, so we only have to wait for a single user.

Waiting for sidekiq jobs to complete in the HTTP request/response cycle is failure-prone, e.g., during deploys. Since we're only waiting for a single user, we might as well do that inline instead..

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• [ ] Documentation created/updated/strile>
• [ ] API support added
• Tests added for this feature/bug
• Review
  • Has been reviewed by Backend
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together

What are the relevant issue numbers?

Closes #36792 (closed)