Add component Flags to astro deployment logs

[ichung08]

Description

Describe the purpose of this pull request.

Users need to see logs for a specific component (webserver, scheduler, triggerer, worker) of a Deployment. This change will allow users to set specific flags (--webserver) to parse a specific component's flags.

🎟 Issue(s)

Related #1590

🧪 Functional Testing

List the functional testing steps to confirm this feature or fix.

• Updated unit tests and added new units
• CLI Testing:
• no flags set:

• all flags set:

  

• webserver only:

  

• scheduler only:

  

• triggerer only:

  

• worker only:

  

📸 Screenshots

Add screenshots to illustrate the validity of these changes.

📋 Checklist

• [x] Rebased from the main (or release if patching) branch (before testing)
• [x] Ran make test before taking out of draft
• [x] Ran make lint before taking out of draft
• [x] Added/updated applicable tests
• [ ] Tested against Astro-API (if necessary).
• [ ] Tested against Houston-API and Astronomer (if necessary).
• [ ] Communicated to/tagged owners of respective clients potentially impacted by these changes.
• [ ] Updated any related documentation

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 88.88889% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 86.74%. Comparing base (1a67fff) to head (d15ea33).

Files	Patch %	Lines
cloud/deployment/deployment.go	84.61%	1 Missing and 1 partial :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1633 +/- ## ========================================== - Coverage 86.75% 86.74% -0.01% ========================================== Files 114 114 Lines 16661 16671 +10 ========================================== + Hits 14454 14462 +8 - Misses 1318 1319 +1 - Partials 889 890 +1 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.