Add documentation for resolving Collector breaks

[nslaughter]

Is your feature request related to a problem? Please describe. Currently releasers may have various backgrounds in the components of OpenTelemetry and may have to individually formulate a workflow or muddle through this process as a one-off. However, changes like this should be expected and managing this is an important aspect of releasing the latest versions.

Describe the solution you'd like A clear and concise description of how to resolve breaking changes (usually names, module location, and sometimes function signatures or other types). The description should expand the group who can maintain and provide a straightforward workflow for the light refactoring required.

Describe alternatives you've considered More automation was considered, but this approach is a more achievable starting point and likely will be all that's needed.

Additional context This came up in the latest release with the processor.CreateSettings deprecation, which needs light refactoring.