Show debugger attach message (#21483)

Also spruce up branding

Author: pranavkm

src/Components/Web.JS/dist/Release/blazor.webassembly.js

@@ -10,22 +10,22 @@ export function hasDebuggingEnabled() {
 }
 
 export function attachDebuggerHotkey(resourceLoader: WebAssemblyResourceLoader) {
+  hasReferencedPdbs = !!resourceLoader.bootConfig.resources.pdb;
+
   // Use the combination shift+alt+D because it isn't used by the major browsers
   // for anything else by default
   const altKeyName = navigator.platform.match(/^Mac/i) ? 'Cmd' : 'Alt';
   if (hasDebuggingEnabled()) {
     console.info(`Debugging hotkey: Shift+${altKeyName}+D (when application has focus)`);
   }
 
-  hasReferencedPdbs = !!resourceLoader.bootConfig.resources.pdb;
-
   // Even if debugging isn't enabled, we register the hotkey so we can report why it's not enabled
   document.addEventListener('keydown', evt => {
     if (evt.shiftKey && (evt.metaKey || evt.altKey) && evt.code === 'KeyD') {
       if (!hasReferencedPdbs) {
         console.error('Cannot start debugging, because the application was not compiled with debugging enabled.');
       } else if (!currentBrowserIsChrome) {
-        console.error('Currently, only Edge(Chromium) or Chrome is supported for debugging.');
+        console.error('Currently, only Microsoft Edge (80+), or Google Chrome, are supported for debugging.');
       } else {
         launchDebugger();
       }

src/Components/Web.JS/src/Platform/Mono/MonoDebugger.ts

@@ -58,7 +58,7 @@ Ensure your browser is running with debugging enabled.
     {GetLaunchChromeInstructions(targetApplicationUrl)}
 </p>
 <p>
-    <h4>If you are using Microsoft Edge (Chromium) for your development, follow these instructions:</h4>
+    <h4>If you are using Microsoft Edge (80+) for your development, follow these instructions:</h4>
     {GetLaunchEdgeInstructions(targetApplicationUrl)}
 </p>
 <strong>This should launch a new browser window with debugging enabled..</p>