feat: support terraform nested directories project structure

[moelasmar]

Which issue(s) does this change fix?

#4724

Why is this change necessary?

Currently, customers could not use sam build command on Terraform projects that has a nested directories structure.

How does it address the issue?

Customers can pass a new parameter --terraform-project-root-path and pass the project root directory path that contains all the nested structures.
for example for this scenario:

/project
  /infrastructure
    envrionment/
        dev/
            dev.tfvars
        test/
            test.tfvars
    main.tf
    providers.tf
  /src
    ... (lambda code) ...
  /tests
    ... (lambda tests) ...

customers can execute sam build command from this path /project/infrastructure where the Terraform root module configuration files exist, and pass the value of the new parameter --terraform-project-root-path as ./.. or /project.

SAM CLI will use the value passed in the new parameter to set the ProjectRootDirectory property in all the lambda functions/layers metadata properties, and so Lambda Builders will be able to determine which directory that will be copied to the Temporary directory, and then run the building logic.

What side effects does this change have?

N/A

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.