fix: modify alert commands to work with new API (#38389)

* fix: modify alert commands to work with new API (#38085)

* fix: modify alert commands to work with new API

* chore: update release notes

* chore: run format

* chore: bump demisto docker version

* feat: alter columns in alerts list

* Fix ST110 validation

* Address ST-111 validation

---------

Co-authored-by: Mariano Mendez <[email protected]>
Co-authored-by: TalZich <[email protected]>

Packs/SecurityScorecard/Integrations/SecurityScorecard/README.md

@@ -209,8 +209,8 @@ Create alert based on grade.
 | --- | --- | --- |
 | change_direction | Direction of change. Possible values are: rises, drops. | Required | 
 | score_types | Comma-separated list of risk factors to monitor. Possible values are 'overall', 'any_factor_score', 'network_security', 'dns_health', 'patching_cadence', 'endpoint_security', 'ip_reputation', 'application_security', 'cubit_score', 'hacker_chatter', 'leaked_information', 'social_engineering'. | Required | 
-| target | What do you want to monitor with this alert. This argument is required if the `portfolios` argument is not specified. Possible values are: my_scorecard, any_followed_company. | Optional | 
-| portfolios | A comma-separated list of Portfolios. to use as a target for the alert. This argument is require if the `target` argument is not specified. You can get a list of portfolios by running `!securityscorecard-portfolios-list`. | Optional | 
+| target | What do you want to monitor with this alert. This argument is required if the `portfolio` argument is not specified. Possible values are: my_scorecard, any_followed_company. | Optional | 
+| portfolio | A portfolio_id to use as a target for the alert. This argument is required if the `target` argument is not specified. You can get a list of portfolios by running `!securityscorecard-portfolios-list`. | Optional | 
 
 #### Context Output
 
@@ -234,8 +234,8 @@ Create alert based threshold met.
 | change_direction | Direction of change. Possible values are: rises_above, drops_below. | Required | 
 | threshold | The numeric score used as the threshold to trigger the alert. | Required | 
 | score_types | Comma separated list of risk factors to monitor. Possible values are 'overall', 'any_factor_score', 'network_security', 'dns_health', 'patching_cadence', 'endpoint_security', 'ip_reputation', 'application_security', 'cubit_score', 'hacker_chatter', 'leaked_information', 'social_engineering'. For multiple factors, provide comma-separated list, i.e. leaked_information,social_engineering. | Required | 
-| target | What do you want to monitor with this alert. This argument is required if the `portfolios` argument is not specified. Possible values are: my_scorecard, any_followed_company. | Optional | 
-| portfolios | A comma-separated list of Portfolios. to use as a target for the alert. This argument is require if the `target` argument is not specified. You can get a list of portfolios by running `!securityscorecard-portfolios-list`. | Optional | 
+| target | What do you want to monitor with this alert. This argument is required if the `portfolio` argument is not specified. Possible values are: my_scorecard, any_followed_company. | Optional | 
+| portfolio | A portfolio_id to use as a target for the alert. This argument is required if the `target` argument is not specified. You can get a list of portfolios by running `!securityscorecard-portfolios-list`. | Optional | 
 
 #### Context Output
 
@@ -257,7 +257,6 @@ Delete an alert.
 | **Argument Name** | **Description** | **Required** |
 | --- | --- | --- |
 | alert_id | Alert ID. | Required | 
-| alert_type | Type of Alert to delete. Possible values are: score, grade. | Required | 
 
 #### Context Output