Add editable field to suppression rule (#2021)

Co-authored-by: ci.datadog-api-spec <[email protected]>
Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com> a517064

Author: api-clients-generation-pipeline[bot]

datadog_api_client.v2.model.html

@@ -33939,6 +33939,7 @@ <h2 id="submodules">Submodules<a class="headerlink" href="#submodules" title="Li
 <li><p><strong>creator</strong> (<a class="reference internal" href="#datadog_api_client.v2.model.security_monitoring_user.SecurityMonitoringUser" title="datadog_api_client.v2.model.security_monitoring_user.SecurityMonitoringUser"><em>SecurityMonitoringUser</em></a><em>, </em><em>optional</em>) – A user.</p></li>
 <li><p><strong>data_exclusion_query</strong> (<em>str</em><em>, </em><em>optional</em>) – An exclusion query on the input data of the security rules, which could be logs, Agent events, or other types of data based on the security rule. Events matching this query are ignored by any detection rules referenced in the suppression rule.</p></li>
 <li><p><strong>description</strong> (<em>str</em><em>, </em><em>optional</em>) – A description for the suppression rule.</p></li>
+<li><p><strong>editable</strong> (<em>bool</em><em>, </em><em>optional</em>) – Whether the suppression rule is editable.</p></li>
 <li><p><strong>enabled</strong> (<em>bool</em><em>, </em><em>optional</em>) – Whether the suppression rule is enabled.</p></li>
 <li><p><strong>expiration_date</strong> (<em>int</em><em>, </em><em>optional</em>) – A Unix millisecond timestamp giving an expiration date for the suppression rule. After this date, it won’t suppress signals anymore.</p></li>
 <li><p><strong>name</strong> (<em>str</em><em>, </em><em>optional</em>) – The name of the suppression rule.</p></li>