[BuildCheck Suggestion]: Flag usage of the Warning or Error Tasks without an associated Code

[baronfel]

Summary

When Warning or Error is used without Code, users lose the ability to manage the severity of the Warning or Error. This can lead to situations with impossible-to-work-around warnings leading to an overall worse user experience.

Background and Motivation

This bit the containers targets here - we should not have been able to write this logic and should have been forced to create a Code.

Sample issue or antipattern that the check should be flagging

See above

Sample output

BC0666: Warning and Error Tasks should not be used without passing the Code parameter