E6/S1: tag apiEndpoint with SCOPE

[jimhw]

Allow a user to specify the OAuth2 tag within a pipeline's path to match all endpoints URLs

Example:
condition: ["always"]
or by a particular path
condition: ["pathExact", "/protected/resourceA"]
this would trigger the policy.

[jimhw]

Should be part of #17. Need to verify

[jimhw]

Depends on RBACL #46

[altsang]

no longer dependent on #46

[altsang]

per discussion with @DrMegavolt - we will add scopes as a attribute to the endpoint without a tag action as originally specified by Roman, Scopes will need to require the ability to specify granularity to the HTTP VERB level

[altsang]

in API endpoint - scopes can be defined as shown in example below:

*.dog.com + /v1/api/cart + GET, assign scope STAFF
*.dog.com + /v1/api/catalog + GET, assign scope STAFF
*.dog.com + /v1/api/customer + GET, assign scope STAFF

apiEndpoints
dogEndpoint:
host: .dog.com
path: /v1/api/
scopes: scopes:{{ scope:staff, verbs:{GET}}, { scope:admin,verbs:{ GET, PUT, POST, DELETE}}
- scope:
name: STAFF
verbs: GET
- scope:
name: ADMIN?
verb: [GET, POST, PUT DELETE]

*.dog.com /v1/api/cart + GET, PUT, POST, DELETE, assign scope ADMIN
*.dog.com/v1/api/catalog + GET, PUT, POST, DELETE, assign scope ADMIN
*.dog.com/v1/api/customer + GET, PUT, POST, DELETE, assign scope ADMIN