API cleanup

[himdel]

API refactor to

• not rely on inheritance - having an explicit list of methods per api should make it clearer what is and isn't available, as well as find unused code
• not rely on apiPath context - having the api paths spelled out in template strings makes it easier to search methods by url
• slightly decrease logic in api code - ideally the first api layer is 1:1 with actual endpoints, with helpers above it, but not quite there yet

The interface remains largely unchanged outside of src/api,
auth is moved from BaseAPI to PulpAPI.

The available methods are

• base.list(url, params?) - does a GET and translates params (sort and page/page_size)
• base.http.get(url) - does a GET
• base.http.post(url, data) - does a POST
• base.http.delete(url) - does a DELETE
• base.http.put(url, data) - does a PUT
• base.http.patch(url, data) - does a PATCH

and cleanup more dead code related to is_anonymous, feature flags and hub settings.

(Follow-up with consolidating by plugin and replacing galaxy apis.)

[gerrod3]

Do we need to merge this first or the config.json change first? They conflict right?

[himdel]

Oh, the conflict was just about config., rebased :)