feat: Add remote invoke implementation for Kinesis stream service for put_record API

[hnnasit]

Which issue(s) does this change fix?

N/A

Why is this change necessary?

This PR adds the implementation for remote invoke support for Kinesis stream service. The boto3 API put_record is called when sam remote invoke is run to put a record to the provided kinesis stream name using event or event-file.

How does it address the issue?

• The Data of the record which is a required field can be provided using event or event-file parameters which will get encoded as base64 and put into Kinesis stream. If no event or event-file is provided, {} is used as Data for putting a record. The event is loaded using json before passing to boto3 API and the event-file is read and directly passed to boto3 API.
• The PartitionKey is a required field for boto3 API and so it is randomly generated if not provided as input. This is just used to determine which Shard does the record get added to using a MD5 hash function.
• The other fields such as ExplicitHashKey, SequenceNumberForOrdering, and StreamARN can be provided as strings using the --parameter field

Use cases:

1. sam remote invoke KinesisStreamLogicalId --stack-name sam-app --event '{"hello": "world", "foo": 1, "bar": {}}': Puts a record with provided event as data to the KinesisStreamLogicalId Kinesis stream.

{
  "ShardId": "shardId-000000000000",
  "SequenceNumber": "sequence-number"
}

3. sam remote invoke arn:aws:kinesis:us-east-1:12345678910:stream/kinesis-stream-name --event "hello world": Kinesis stream Arn used as resource-id to put a record
4. sam remote invoke kinesis-stream-name --event "hello world" --output json: Kinesis stream name used as resource-id to put a record

{
  "ShardId": "shardId-000000000000",
  "SequenceNumber": "sequence-number",
  "ResponseMetadata": {}
}

What side effects does this change have?

No side effects.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[hawflau]

LGTM. just one minor typo