Should @access(false) imply removal of that API

[ramnivas]

Currently, @access(false) (and its versions, such as @access(query=..., mutation=false) mean the API is available but not usable by anyone.

Another possible interpretation is to remove the API from our schema altogether. If/when we do this, we can introduce another possible value, private (as in @access(private)), to make the API available only through the ExoPriv object.

Do we want a mode (during development), where the @access(false) APIs can be seen from GraphiQL. This way developers, for example, are aware of their possible existence and may change the access control if needed.

[ramnivas]

Kind of need to sort #480. If a user starts out with default @access(false), there will be no queries and hence introspection will fail.