- Due to https://github.com/exAspArk/batch-loader/pull/32,
we  changed BatchLoader.for into BatchLoader::GraphQL.for
- since our results are wrapped in a BatchLoader::GraphQL,
calling `sync` during authorization is required to get real object
- `graphql` now has it's own authorization system.  Our
`authorized?` method conflicted and required renaming

The current state of group issue boards does not show the "Add issues"
button on the UI for users that are reporters of group child projects.

so that we can use API::Internal namespace.

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/61927.

Remove spec/rails_helper.rb

Closes #66741

See merge request gitlab-org/gitlab-ce!32380

It performs an expensive operation, but isn't required in
most of tests

rails_helper.rb's only logic was to require
spec_helper.rb.

Fix snippets API not working with visibility level

Closes #66050

See merge request gitlab-org/gitlab-ce!32286

Standardize use of `content` parameter in snippets API

Closes #66673

See merge request gitlab-org/gitlab-ce!32296

There was some confusion over whether `code` or `content` is the right
parameter for snippets. Internally, the database stores
`content`. However:

1. Project snippets use `code`. `code` gets remapped in `content` in
`lib/api/project_snippets.rb`.

2. Personal snippets use `content`.

To unify these APIs, allow an alias of `content` to work for project
snippets.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66673