to match API::Internal to API::Internal::Base rename

We want the ability to restrict access for Git activity when smartcard
authentication is used. Git does not support smartcards yet but we can
check if the user has a valid browser session where smartcard
authentication was used.

Includes changes to use stub_licensed_features

Both API and feature will only be available for customers
with GitLab Premium license.

This allows uploading designs through GraphQL.

The mutation requires these arguments:

- `fullPath`: The path in which we can find the issue for creating
  designs
- `iid`: The iid of the issue in which to upload designs
- `files`: An array of files. We expect these to be in the format
  used by apollo-upload-client[0] which uses this spec[1] for
  multipart fileupload.

The middleware used for handling the multipart upload an translating
the variables is apollo_upload_server[2]

When a file is uploaded, the basename is used for creating a design,
when a design for the specified issue did not exist for the filename,
a new one is created. Otherwise the existing one is used.

When uploading a new file, a new version is created an linked to the
design being updated or created.

The files are stored in a repository that lives next to the project
repository with the path `@hashed/[hash]/[to]/[repo].design.git. The
files are not yet stored in LFS, but they should be.

0: https://github.com/jaydenseric/apollo-upload-client
1: https://github.com/jaydenseric/graphql-multipart-request-spec
2: https://github.com/jetruby/apollo_upload_server-ruby

This reverts commit 0c4a25f3, reversing
changes made to 6513028e.

This reverts commit cfed90dc, reversing
changes made to a1e84c1a.

Explicitly requiring `Gitlab::GlRepository` in the spec that requires
it makes sure it is correctly prepended with
`EE::Gitlab::Repository`.

Otherwise, if a spec before it autoloaded one of the constants from
within `Gitlab::GlRepository` the module would not be prepended.

This allows uploading designs through GraphQL.

The mutation requires these arguments:

- `fullPath`: The path in which we can find the issue for creating
  designs
- `iid`: The iid of the issue in which to upload designs
- `files`: An array of files. We expect these to be in the format
  used by apollo-upload-client[0] which uses this spec[1] for
  multipart fileupload.

The middleware used for handling the multipart upload an translating
the variables is apollo_upload_server[2]

When a file is uploaded, the basename is used for creating a design,
when a design for the specified issue did not exist for the filename,
a new one is created. Otherwise the existing one is used.

When uploading a new file, a new version is created an linked to the
design being updated or created.

The files are stored in a repository that lives next to the project
repository with the path `@hashed/[hash]/[to]/[repo].design.git. The
files are not yet stored in LFS, but they should be.

0: https://github.com/jaydenseric/apollo-upload-client
1: https://github.com/jaydenseric/graphql-multipart-request-spec
2: https://github.com/jetruby/apollo_upload_server-ruby