[FR]: Add support for py_library dependencies in aws_py_lambda rule

[wevonosky]

What is the current behavior?

Currently py_library dependencies are seemingly ignored by the implementation of the _py_lambda_tar rule. This presents problems for organizations which maintain internal libraries that they want their lambdas to be able to depend on.

For example:

aws_py_lambda(
    name = "image",
    entry_point = "lambda_function.py",
    deps = [requirement("requests"), "//path/to/internal/lib"],
)

oci_tarball(
    name = "tarball",
    image = ":image",
    repo_tags = ["aws_lambda_hello_world:latest"],
    visibility = [":__subpackages__"],
)

results in no trace of the internal lib in the image that gets created when calling bazel run :tarball.

Describe the feature

py_library dependencies should be included when creating a aws_py_lambda image.