feat: Add response_streaming_invoke_arn to outputs

[joaquingatica]

Description

Add lambda_function_response_streaming_invoke_arn output which is a direct forward of the existing aws_lambda_function.response_streaming_invoke_arn output.

Motivation and Context

As of now, if the Response Streaming Invoke ARN is needed outside of this module, it has to be derived from the invoke_arn when it should be able use the native output of the aws_lambda_function resource instead.

One example is when streaming responses from API Gateway, something similar to the following is needed to use as uri in an aws_api_gateway_integration when response_transfer_mode = "STREAM" is used:

resource "aws_api_gateway_integration" "myapi_resource_post" {
  # other attributes...
  response_transfer_mode  = "STREAM"
  uri = replace(
    replace(
      module.mylambda.lambda_function_invoke_arn,
      "2015-03-31", "2021-11-15"
    ),
    "/invocations", "/response-streaming-invocations"
  )
}

Instead, the following could be done when using the output added through this PR:

resource "aws_api_gateway_integration" "myapi_resource_post" {
  # other attributes...
  response_transfer_mode  = "STREAM"
  uri = module.mylambda.lambda_function_response_streaming_invoke_arn
}

The workaround is inspired by the suggestion in hashicorp/terraform-provider-aws#45649

Breaking Changes

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I updated examples/complete by adding a new output to it which forwards the module's output
  • Its README.md was updated accordingly via terraform-docs
• I have tested and validated these changes using one or more of the provided examples/* projects
  • After performing terraform apply, the new output was printed to the CLI.
  • This is the relevant line (I replaced my AWS account number with XXXXXXXXXXXX):
    lambda_function_response_streaming_invoke_arn = "arn:aws:apigateway:eu-west-1:lambda:path/2021-11-15/functions/arn:aws:lambda:eu-west-1:XXXXXXXXXXXX:function:capable-crayfish-lambda1/response-streaming-invocations"
• I have executed pre-commit run -a on my pull request

[joaquingatica]

Do let me know if this qualifies as "significant work" as per the CONTRIBUTING.md guidelines and I'll happily open an Issue to track discussions.

I feel like it's small enough to not be considered significant, but could be wrong.

Thank you!

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[joaquingatica]

Still a relevant change, commenting to remove stale status.