Contributor Docs: Add a Default Breaking Change section

[mbfrahry]

Community Note

• Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
• Please do not leave "+1" or "me too" comments, they generate extra noise for PR followers and do not help prioritize for review

Description

Adding a section to the contributor docs around how breaking changes can occur when adding Default Values.

PR Checklist

• I have followed the guidelines in our Contributing Documentation.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
• I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
• I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
  For example: “resource_name_here - description of change e.g. adding property new_property_name_here”

This is a (please select all that apply):

• Bug Fix
• New Feature (ie adding a service, resource, or data source)
• Enhancement
• Breaking Change
• Documentation

[stephybun]

Thanks @mbfrahry, I left a couple of suggestions on the guide, would you mind taking a look through them?

[stephybun]

I feel like there's supposed to be some example of the diff output here after like so:, but it looks like it was provided further down, maybe remove like so: here?

Suggested change

	But if we do that, people who have created that resource without the attribute specified will see a plan diff when upgrading to this version of the provider like so:
	But if we do that, people who have created that resource without the attribute specified will see a plan diff when upgrading to this version of the provider.

[stephybun]

Rename this to guide-breaking-changes.md

[github-actions]

This PR is being labeled as "stale" because it has not been updated for 30 or more days.

If this PR is still valid, please remove the "stale" label. If this PR is blocked, please add it to the "Blocked" milestone.

If you need some help completing this PR, please leave a comment letting us know. Thank you!

[mbfrahry]

Done! Sorry for the delay here

[tombuildsstuff]

@mbfrahry still some pending comments on this one?

[mbfrahry]

Missed that rename. Taken care of

[katbyte]

LGTM ☎️