User experience improvements for QIR generation

[cesarzc]

• Underline span in user code that caused a QIR generation error in the vscode extension. Currently, only a pop-up with the error message appears (Use package spans in partial evaluation #1547, Surface partial evaluation errors in VS Code #1552).
• Provide a visual cue in the vscode extension to indicate QIR generation is in progress. (Add notification with cancel to VS Code for QIR code gen #1591)
• Extend @Config syntax to allow performing not unary operator (Support logical not in @Config attribute #1564)
• Error messages that refer to support by current "target" should clarify when it is meant to be "target profile" vs "submission target" (it's usually the former) (Support error Uri, update RCA error strings #1575)
• Add error specific help links for RCA check pass errors (current all redirect to the wiki) (Use error-specific links for RCA check pass errors #1594)

Add lints that nudge users to use more robust patterns when compiling for hardware targets Lint suggestions moved to #1333 for tracking.