fix(manifest): component <name> must be element-safe (com_mokosuitebackup)

The "Type - Name" convention (commit d155958) set the component <name> to
"Component - MokoSuiteBackup". Joomla derives a component's element from its
<name> (com_ + sanitized name), so this produced element
`com_component-mokosuitebackup` instead of `com_mokosuitebackup`. On update,
Joomla registered a NEW component (new element + folder) at the current
version and orphaned the real `com_mokosuitebackup` at its old version — which
is what `?option=com_mokosuitebackup` and the admin menu still load. Net
effect: the component appears "stuck" on the old version with the old UI.

Revert the component <name> to "MokoSuiteBackup" (-> com_mokosuitebackup) and
document why the display convention must not be applied to a component's
<name>. Packages are exempt (they use <packagename>); plugins/modules are
exempt (<name> is only a display label there).

Refs #171-area remote tab reports; fixes the duplicate-component registration.

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i

source/packages/com_mokosuitebackup/mokosuitebackup.xml

@@ -6,7 +6,17 @@
  * @license     GNU General Public License version 3 or later; see LICENSE
  -->
 <extension type="component" method="upgrade">
-	<name>Component - MokoSuiteBackup</name>
+	<!--
+		IMPORTANT: a component's <name> drives the Joomla-derived extension
+		element (com_ + sanitized name), so it MUST stay element-safe:
+		"MokoSuiteBackup" -> com_mokosuitebackup. Do NOT apply the "Type - Name"
+		display convention here — "Component - MokoSuiteBackup" derives
+		com_component-mokosuitebackup, which registers a duplicate component and
+		orphans the real one. Packages are exempt because they set the element
+		via <packagename>; plugins/modules are exempt because <name> is only a
+		display label there.
+	-->
+	<name>MokoSuiteBackup</name>
 	<version>02.56.07</version>
 	<creationDate>2026-06-02</creationDate>
 	<author>Moko Consulting</author>