chore: update definition of breaking change in CONTRIBUTING.md

[samson-keung]

Issue # (if applicable)

N/A

Reason for this change

The paragraph removed in this PR is too restrictive in defining breaking changes. It states that ANY change that may stop ANY CDK application to "not work correctly" is a breaking change. It is missing the point that we do not guarantee CDK applications that have custom logic or overriding CDK classes/methods, to not break. A recent case of this is #33319

Description of changes

Given that there is more concrete information on what defines a Breaking Change further down in CONTRIBUTING.md, I have removed the inaccurate paragraph

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

(This review is outdated)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.92%. Comparing base (2ca12eb) to head (b4bde3b).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #33368   +/-   ##
=======================================
  Coverage   80.92%   80.92%           
=======================================
  Files         236      236           
  Lines       14253    14253           
  Branches     2490     2490           
=======================================
  Hits        11534    11534           
  Misses       2434     2434           
  Partials      285      285           

Flag	Coverage Δ
suite.unit	80.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	79.73% <ø> (ø)
packages/aws-cdk-lib/core	82.20% <ø> (ø)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: b4bde3b
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[QuantumNeuralCoder]

Can you add "reason for this change" explanation to the readme possibly with the issue pointer? Its a great explanation. Removing this section will open up a debate on what and what is not a breaking change.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.