Better implementation of breaking change notifications

## Description of the new feature
I like the idea with breaking change notification. What I don't like is that - in cases when code can work "old" and "new" way - breaking change notification occurs even when I update the code to be aligned to upcoming change - even if my code is ready for a breaking change, I still get notified. In such cases, it would be more logical that breaking change notification only occurred when code uses constructs that are being deprecated
Example:
```
WARNING: Upcoming breaking changes in the cmdlet 'Get-AzManagementGroup' :
- The parameter : 'GroupName' is being replaced by parameter : 'GroupId'.
- Change description : We will repleace GroupName with GroupId to make it more clear.
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.
```

I changed the code so as it uses the GroupId parameter instead of GroupName, but after the change, I still get notified about breaking change - unnecessarily, because my code does not use deprecated parameter any more.

I would like to see breaking change notification only when my code uses featires being deprecated. I'm aware that this may not be possible in all cases, but for relevant scenarios, such as the one described above, it would increase value of breaking changes notifications

Thank you
Jiri