Removing all references to python-oauth2
Consumer cleanup.

  - Removed untested/redundant methods.  One of them was probably
    incorrect anyway.
  - Equality for consumer established.
Re-establishing consumer validation.
Rename scope_id to realm.

  - Since scope_id essentially capture the essence of a realm, where a
    defined manager controls access to a subset of data within a site
    based on what is permitted by the scope specified.
Remove realm completely, in retrospect.

  - Realms don't exist in OAuth2, so porting this concept over will be
    problematic at best.
  - We also have layers for registering the scope manager.  Integrators
    should use these instead.
General redesign

  - Token manager is now agnostic to request objects.  Just take in
    the actual string parameters for the things that are outside the
    scope of the TokenManager (i.e. consumers - it doesn't care about
    the implementation details of it, like secrets).
  - Dedicated method to return RequestTokens.
  - Test cleanup to reflect this fact, and spell things out better
    where applicable.
Builtin the dummy token.
Formalized verification of request token

  - Also verify that the consumer key from request and the one stored
    matches.
Integration of oauthlib.

  - Dropped the OAuth utility since everything (for now) is coordinated
    by the OAuth PAS Plugin.
  - TokenManager updated to provide the features needed by oauthlib,
    namely the clearer separation of token types (request/access),
    relaxed fallbacks as the plugin now handles the raising of errors
    to counter timing attacks, and more stringent token verification
    process.
  - Tests have been updated.  Some python-oauth2 legacy remains, but
    they will be replaced in time.  Some output and tests have been
    modified to conform to oauthlib's intrepretation of correctness.
  - Tests removed are related to the now unused classes.
  - Integration testing in the form of doctests still pending.
Turn the oauthlib server into an adapter

  - This removes a few indirection in the relationship.  The PAS plugin
    now only cares about a lot less implementation details.
  - Reworked the scope completely.  No longer accepts tokens and only
    deals in identifier of client/access keys.
Preliminary changes noted in changelog.
Raise an exception if neither are true.

  - Not sure how this can happen, but this makes the intention a bit
    more clear.
Remove the declaration for the removed utility.
Checking cleanup

  - Scope no longer part of a token.
  - TokenManager no longer does complete token verification.
  - The verification method provided only checks for the verifier.
  - The OAuth utility will be checking/calling the methods during the
    comprehensive verification process.
Callback is now an ascii string.

  - Encode URI as ascii strings because that is what they are, not
    unicode.
  - Remove the confirm field because it can be derived from the callback
    field.
Add the getValidated consumer method back in.

  - Use it at where applicable in the plugin itself.
Reworked how scope is checked.

  - The real implementation for this should be done as a SecurityManager
    and not within this credential plugin, but it can work here.
  - Make use of the parent PAS private method to capture the values that
    are now required to evaluate scope validity.
Scope redesign and doctest cleanup.

  - DefaultScopeManager complete redesign - scope based on content types
    and view names permitted rather than raw urls; reimplmeentation is
    provided but mostly untested (see doctest).
  - The doctests using the previous method of instantiating requests are
    rewritten; tests related to previous scope implementation removed.