[patch] Support Let's Encrypt HTTP-01 for path routing mode

[praiyani6789]

Description

Adds Let's Encrypt HTTP-01 certificate management as an opt-in feature for MAS installs using path-based routing. Introduces new CLI flag --le-email [ACME email], interactive prompts, non-interactive validation, install summary output, and Tekton pipeline wiring. Also add unit tests for new flag to cover edge cases.

• Interactive mode: after routing mode is confirmed as path, prompts the user to opt into Let's Encrypt and collects the email address.
• Non-interactive mode: pass --le-email [ACME email] to enable let's encrypt, it validates that --le-email [ACME email] is only used with --routing path.

NOTE: Let’s Encrypt can work with both custom and default domains. Therefore, we can use Let’s Encrypt http01 in mas for default domains instead of using a self-signed CA. Core can use the Let’s Encrypt issuer to obtain the public certificate and then pass it to the other applications in path mode.

Jira Issue

MASCORE-13570

Guidance for Reviewers

• Before merging this PR, the following PR must be merged first:
  [patch] Support Let's Encrypt HTTP-01 issuer in suite_dns role ansible-devops#2434
  [patch] Wire Let's Encrypt HTTP-01 params into install PipelineRun template python-devops#485

Testing

• Interactive mode:

• Non-interactive mode validations:

• Summary preview:

• Test on ibm cloud: