Should we add a "breaking change" label in GitHub?

### Is your feature request related to a problem or challenge?

We have an "api change" label to indicate breaking API changes, but this doesn't seem appropriate for indicating changes to query execution behavior that produce different results when compared to earlier releases.

I wonder if we should add a "breaking change" label as well?

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Start by reviewing the existing "api change" label and the issue's discussion about query execution changes. Done means reaching a documented decision on whether a separate "breaking change" label is needed and defining when it should be used.

Written by the indexing model from the issue text.