- Introduce support for parsing distributed tracing information for HTTP based
  trigger invocations of the instrumented Lambda function
- Both AWS API Gateway versions 1.0 and 2.0 are supported
- For web driven invocations of an instrumented function, categorize the
  invocation as being "web" based, and record relevant HTTP information
  including the method, URI, and status code post invocation.
- Recognize and report on fully 12 separate AWS resources that are capable of
  triggering a Lambda function invocation: ALB, API Gateway V1, API Gateway V2,
  CloudFront, CloudWatch Scheduler, DynamoStreams, Firehose, Kinesis, S3, SES,
  SNS, and SQS.
- If an AWS resource based trigger is identified, record at least the type
  of the resource and the relevant arn. For many resources, also record
  additional context specific information. For example, for an S3 based
  invocation, record the S3 bucket name.

- utilize the constant pointing to the JSON source file
- only read from the JSON source file once

for the dozen AWS resources under test, require Ruby 3.2+

skip unless Ruby v3.2+ (minimum available AWS Lambda runtime)

constrain all relevant tests to Ruby 3.2+

don't destructively alter the hash - use #dup instead

Co-authored-by: Hannah Ramadan <76922290+hannahramadan@users.noreply.github.com>

tense fix for lambda updates

Co-authored-by: Kayla Reopelle <87386821+kaylareopelle@users.noreply.github.com>

use bullets for the lambda enhancements

Co-authored-by: Kayla Reopelle <87386821+kaylareopelle@users.noreply.github.com>

remove `rescue` that was intended to be temporary

use `each_value` instead of `each` with `_key`

the serverless handler is only used with Ruby v3.2+, so only test with
Ruby v3.2+

removed redundant freezing