Initial release and plugin review

[srtfisher]

In addition to the changes in this PR please also review the following files which have not been code reviewed previously:

• https://github.com/alleyinteractive/wp-command-palette/tree/develop/services/commands
• https://github.com/alleyinteractive/wp-command-palette/tree/develop/entries/app-block-editor
• https://github.com/alleyinteractive/wp-command-palette/tree/develop/entries/app-outside-block-editor

[attackant]

Approving 🐙 but please review:

• Should this be hard coded to false? and here vs using some other kind of state variable?
• Do we need some kind of sanitization here? and here?
• same question for window.location.href calls in this file
• And then here in this file, we could DRY things a bit if we wanted to

const createCommand = (
  element: Element, 
  namePrefix: string, 
  labelTemplate: string, 
  icon: React.ComponentType
): Command => ({
  name: `wp-command-palette/${namePrefix}-${slugify(element.textContent || namePrefix)}`,
  label: sprintf(labelTemplate, element.textContent),
  callback: () => {
    window.location.href = element.getAttribute('href') || '';
  },
  icon,
});
if (mySites) {
  index.push(createCommand(
    mySites, 
    'network', 
    __('Go to: Network - %s', 'wp-command-palette'),
    globe
  ));
}

if (networkAdmin) {
  index.push(createCommand(
    networkAdmin,
    'network-admin',
    __('Go to: Network Admin Dashboard', 'wp-command-palette'),
    globe
  ));
}

// ... and so on for other elements

I have never used the command palette, i do not think

[srtfisher]

I changed it to be link.click() in many places instead of window.location.href = '...'.