fix(ApplicationLogs): reject invalid getapplicationlog triggerType

[cschuchardt88]

Docs say an invalid trigger throws. Enum.TryParse failing skipped the filter, so callers got unfiltered executions. Numeric strings such as 16 also parsed as undefined enum values.

Require a named TriggerType or return InvalidParams.

Independent of other PRs.

[codecov]

Codecov Report

❌ Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 51.42%. Comparing base (e56bcce) to head (74cdc5d).

Files with missing lines	Patch %	Lines
plugins/ApplicationLogs/LogReader.cs	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##           master-n3    #1108      +/-   ##
=============================================
- Coverage      51.48%   51.42%   -0.07%     
=============================================
  Files            284      284              
  Lines          16699    16703       +4     
  Branches        2148     2149       +1     
=============================================
- Hits            8598     8590       -8     
- Misses          7527     7541      +14     
+ Partials         574      572       -2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[shargon]

Isn't TryParse enough?

[superboyiii]

Seems not enough. .NET’s Enum.TryParse accepts numeric strings as well as names. So values like "16" (undefined) or "64" (Application =0x40) both succeed, even though they aren’t named TriggerType values.

[superboyiii]

Tested. It works.