LLViewerWindow::handleKey(): Partial Fix for Issue 704: Keyboard shortcuts that should be passed to focused text fields are instead passed to selected prims when building

All edit keys now work, but Ctrl-A still doesn't work right, it must be grabbed by something else...
Adds LLFocusMgr::keyboardFocusHasAccelerators()
Adds virtual bool LLView::hasAccelerators() which returns false by default, overrides returning true placed in LLPreviewScript and LLPreviewNotecard
Shortcut keys added to notecard and script menu xmls

I'm thinking Qarl's Align tool handling may be receiving the Ctrl-A, we do seem to handle it differently than Exodus and Firestorm something modern could have broken the old way..
Come to think of it, those two features(Align and Select all prims) have a longstanding shortcut conflict in shortcuts... that's pretty nasty

indra/newview/llviewerwindow.cpp

@@ -2723,7 +2723,6 @@ BOOL LLViewerWindow::handleKey(KEY key, MASK mask)
 
 	LLFocusableElement* keyboard_focus = gFocusMgr.getKeyboardFocus();
 
-	/*
 	// give menus a chance to handle modified (Ctrl, Alt) shortcut keys before current focus
 	// as long as focus isn't locked
 	if (mask & (MASK_CONTROL | MASK_ALT) && !gFocusMgr.focusLocked())
@@ -2736,13 +2735,14 @@ BOOL LLViewerWindow::handleKey(KEY key, MASK mask)
 			return TRUE;
 		}
 
+		/* Singu Note: This caused a bug where the menu ate keys before parents of keyboard_focus for some reason, breaking multifloaters usage of ctrl-w to close their selected child floater
 		if ((gMenuBarView && gMenuBarView->handleAcceleratorKey(key, mask))
 			|| (gLoginMenuBarView && gLoginMenuBarView->handleAcceleratorKey(key, mask)))
 		{
 			return TRUE;
 		}
+		*/
 	}
-	*/
 
 	// give floaters first chance to handle TAB key
 	// so frontmost floater gets focus