v0.1.2

Classify REST-JSON operation-as-path services as reads

REST-JSON services such as savingsplans name the operation in the
request path (`POST /DescribeSavingsPlans`) rather than in X-Amz-Target
or an Action parameter. parseAction fell through to `METHOD path`, so
`DescribeSavingsPlans` became `POST /DescribeSavingsPlans`, matched no
read prefix, and landed in the approval queue.

Recover the operation from a lone CamelCase path segment. S3 is excluded
(object keys are arbitrary and could forge a read verdict on a write; S3
reads are gated by HTTP method, not action), and only a single
CamelCase segment matches, so resource-path REST services (lambda,
route53, apigateway) with lowercase or versioned multi-segment paths are
untouched.