Supress validation for a line/file

**Is your feature request related to a problem? Please describe.**
On some workflows, the linter will mark things as *potential* issues because of the way it was written. however, as a writer you have additional information and can possibly conclude that there is no problem. In that situation, having a linter warning is mildly annoying.

For example, I have a workflow that dynamically gets the name of a secret and the accesses `secrets[that value]`. Linter tell me that the context access *might* be invalid. this is correct, but I know that the only possible values should be valid or I've done something wrong elsewhere.

**Describe the solution you'd like**
I'd like to have something along the lines of #pylint: disable etc. for this extension, whether it be a comment ( similar to pylint or eslint ), a config file (e.g. for file x ignore y), an extension setting (ignore warnings of type/ ignore files). To suppress warnings that you know are invalid, to help reduce false positives for issues that the extension simply lacks context for, or to purge warnings that come from bugs of third party workflow authors.

**Additional context**
related: #59

Start by reviewing related issue #59 and the extension's existing warning and reporting entry points. Compare comment, configuration-file, and extension-setting approaches, including how they select warning types and files. Done means a defined, testable suppression mechanism with documented behavior for the example workflow warning.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.