Clarify visibility settings on GitLab.com

Overview

Our visibility settings make sense for a self-managed instance, but they could use clarity for GitLab.com.

The term "Internal", in particular, makes sense to a self-managed instance since that project would be internal to the organization maintaining the instance. "Internal" on GitLab.com, however, is closer to "Public"; on GitLab.com, it merely means that the user would have to register to access the project which is a pretty simple task.

Proposal

Clarify the copy here to clarify that Internal visibility settings are for any registered user on GitLab.com to interact with. Update for both Projects and Groups.

• Change help text from "The project can be accessed by any logged in user." to "The project can be accessed by any registered user on GitLab.com." for GitLab.com only.

Update our documentation to match.