Three Solutions Packaging Fix: Mulesoft, Trend Micro, and ESET UI Metadata Corrected

What Changed

Three solutions received packaging and UI metadata corrections:

• MuleSoft (v3.2.0): Removed a manually hardcoded “Data Connectors: 3 / Learn more” block from the solution description; the packager auto-appends this count, causing it to appear twice in the Create UI Definition blade.
• Trend Micro Cloud App Security (v3.1.0): Updated the “Underlying Microsoft Technologies” list in the solution description to include CCF, Log Ingestion API, and DCRs, reflecting the dual-connector architecture introduced in v3.0.0.
• ESET PROTECT Platform (v3.3.0 repackage): ARM template parameter types corrected from secureString to securestring (case normalisation required for ARM validation); trailing whitespace removed from connector title field.

No YAML content files (Analytic Rules, Parsers, Hunting Queries) were modified. No connector logic or ingestion configuration changed.

Affected Files

Solutions/ESET Protect Platform/Data Connectors/ESETProtectPlatform_API_FunctionApp.json
Solutions/ESET Protect Platform/Data Connectors/azuredeploy_ESETProtectPlatform_API_FunctionApp.json
(packaging artefacts: 3.1.0.zip, 3.2.0.zip, 3.3.0.zip, ReleaseNotes.md, Solution_ESETProtectPlatform.json, Solution_Mulesoft.json, Solution_Trend Micro Cloud App Security.json, createUiDefinition.json, mainTemplate.json)