Related Findings Update Content Addition in SOCRadarIncidentsV4 (demisto#43459)

* Related Findings Update Content Addition in  SOCRadarIncidentsV4 (demisto#43235)

* Change risk score scale from 1000 to 100

It is very important to new joiner

* Related Findings Update Content Addition

* Increase alarm text limit from 1024 to 2048 characters

* Increase alarm_text length limit to 2048 characters

* Update SOCRADAR API endpoint to production URL

* fixed buil test warnings

* pre-commit issues

* fix: replace cached_alarms with last_alarm_ids in both integrations

* testcase updated

* fix: remove emoji assertions from V4 test_fetch tests

* fix: add capfd.disabled() to stdout-producing tests in V4

* fix: README newlines, ruff auto-fixes, and coverage tests

* fix: README newlines, ruff auto-fixes, and coverage tests

* fix: fix test assertions and apply ruff auto-fixes

* fix: apply ruff auto-fixes inline

* style: apply ruff format fixes

* fix: correct test assertions and ruff blank lines

* style: fix remaining ruff blank line issues in MultiTenant

* Add update_related_finding_status and email parameters

Added parameters to specify update behavior and owner email.

* Add update_related_finding_status and email parameters

Added parameters for updating related finding status and email.

* Change 'Show Content' default value to False

* Update README.md

* Increase last_alarm_ids limit from 1000 to 10000

* Rename function argToBoolean to argToBool

* Change API Key type from 4 to 9 in YAML config

* Change default value of show_content to true

* Fix indentation for predefined options in YAML

* Rename function argToBoolean to argToBool

* Fix indentation in update_related_finding_status options

* Change default value of show_content to true

* Change API Key type from 4 to 9

* Change argToBool to argToBoolean for consistency

* Change function name from argToBool to argToBoolean

* Add 'SOCRadar' tag to pack metadata

* Update tags and keywords in pack_metadata.json

Removed the 'SOCRadar' tag and added it to keywords.

* Change API Key type from 9 to 4

* Change API Key type from 9 to 4

* Update 2_2_2.md

* Update 2_2_2.md

---------

Co-authored-by: Radargoger <burak.goger@socradar.io>
Co-authored-by: Kamal Qarain <45042524+kamalq97@users.noreply.github.com>

Author: 3 people

Packs/SOCRadar/Integrations/SOCRadarIncidentsV4/README.md

@@ -100,6 +100,7 @@ To obtain your API credentials:
 | **Max incidents per fetch** | No | 10000 | Maximum incidents per fetch cycle |
 | **First fetch time** | No | 3 days | Initial time range for first fetch |
 | **Fetch Interval (Minutes)** | No | 1 | Time window for subsequent fetches |
+| **Show Content** | No | False | Show Alarm Content Field |
 
 ### Filtering Options
 
@@ -210,11 +211,16 @@ Change the status of one or more alarms.
   - `DUPLICATE`, `PROCESSED_INTERNALLY`, `MITIGATED`, `NOT_APPLICABLE`
 - `comments` (Optional): Status change comments
 - `company_id` (Optional): Override default company ID
+- `update_related_finding_status` (Optional, boolean): If set to true, also update related finding status.
+- `email` (Conditionally Required): Email of action owner. **Required if `update_related_finding_status` is true.**
+
+**Relational Logic:**
+If you select `update_related_finding_status`, you must provide the `email` field.
 
 **Example:**
 
 ```
-!socradar-change-alarm-status alarm_ids="81171696" status_reason="INVESTIGATING" comments="Under review"
+!socradar-change-alarm-status alarm_ids="81171696" status_reason="INVESTIGATING" comments="Under review" update_related_finding_status=true email="analyst@company.com"
 ```
 
 **From Incident Context:**
@@ -638,7 +644,3 @@ SOCRadar is a leading Extended Threat Intelligence (XTI) platform that helps org
 - Ensure supply chain security
 
 Learn more: [www.socradar.io](https://www.socradar.io)
-
----
-
-**Made with ❤️ by the SOCRadar Integration Team and XSOAR teams**