SUGGESTION: Provide a toggle in settings to enable display of message source

[NerdyDeedsLLC]

I love this extension. I love extension_s_. Hell, I WRITE extensions (VSC, Chrome, Firefox, Photoshop), too. My only complaint with VSC's extension system in the practical usage sense (e.g. "working in the document within the editor" vs. "can't find crap when searching VSC extensions") is that this passion of mine results in my getting a LOT of suggestions, icons, decorations, highlights, lowlights, Bud Lites, outlines, suffixes, prefixes, suggested fixes, hints, lightbulbs, blings, pings, dings, wingdings, indicators, diagnostic messages, warnings urging caution, cautions warning urging, underlines, overlines, undermines, overmines, hive-minds, strike-throughs, strike-outs, strikes in general (though surprisingly-few spares; I either hit it outta the park or crash and burn, generally), strike anywhere matches, regex matches, latest matches from match.com, dire errors, error'd dies, gripes, snipes, tripes, likes, dislikes, ventings, preventings, rants, can'ts, shan'ts, pedants, carets, sticks, pointers, and the occasional piece of lint, here and there.

Now, I know your extension is passing stuff along in a more prominent way. I love that story. Gods know I need the clarifying considering the bullyragging I take from all the above. But, like most software, extensions tend to suffer from the same observer bias: that theirs is the only software/extension on earth, and certainly the only one anyone would care to INSTALL. Most software companies do this (Adobe, it's you I'm glaring daggers at, here), and few notice, because (understandably) their developers' heads are generally wrapped around their own work.

But boy, let me tell you: I'd give a pretty to see a prefixed tag in front of every message that came up. Something like:

〘💡[ESLINT] - Improper use of indentation (SomeCodeThatsUnrelatedToDisablingThis)
    Expected 4 spaces, but you only used 3. Your code is bad and you should feel bad. ...Noob 〙

Because occasionally, I'll get something like:

import someEffect from 'someLocation';
someEffect('takesPlace');    〘🖕🖕🖕🖕🖕 🚨**ZOMG! someEffect is not defined!** 
                              Don't worry: We've taken the liberty of correcting the glaring 
                              incompetence in your code for you in this file (the original was 
                              saved with a dot prefix on your neighbor's FireStick), as well 
                              force-pushed the fix to your repo, and sent messages to all your 
                              co-contributors, friends, family, Douglas Crockford, and Linus 
                              Torvalds warning them of what an galactic moron you are._ 〙

Now, it's bad enough when its a matter of the extension not groking some ES6 convention, or their regex missing my edge case...
...it's worse when in fact it IS working just fine and there is manifestly nothing wrong, outside of its own complaining, and of course
...it's worst still when Doug Crockford calls and starts haranguing at me about how my leading commas make me look like "a girly-man" and my yoda declarations "are for pussies" (that guy really WILL hurt your feelings... ask him about eval)
...but then to be unable to figure out which damn extension of the 37 I have running is DOING IT so I can config it or turn the damn thing OFF...

Well, that's just insult to injury yanno?

Anywho, how'd ya feel about an optional [MessageOriginator] prefix?