[beta6] ⚠️ Merge footer_top into footer component

Before doing the change, let's consider why we may wan to keep those components separated: page.html.twig
When we hardcode the call to a component from this template, we make its slots "configurable", because these are the regions where we put the blocks, but not its props. So menus will not be available anymore.

there is a solution cooking on UI SUite USWDS theme:

On theme settings:

  protected function menuSettingsForm($title, $value) {
    $all_menus = $this->entityTypeManager->getStorage('menu')->loadMultiple();
    $menus = [
      "" => "(None)",
    ];
    foreach ($all_menus as $id => $menu) {
      $menus[$id] = $menu->label();
    }
    asort($menus);
    return [
      '#type' => 'select',
      '#title' => $title,
      '#options' => $menus,
      '#default_value' => $value,
    ];
  }

it looks like the links settings type, but simpler.

On page preprocess:

  protected function addRawMenu(array $variables, string $variable, string $menu_id): array {
    $parameters = new MenuTreeParameters();
    // Empty parameters because not configurable.
    $tree = $this->menuLinkTree->load($menu_id, $parameters);
    $manipulators = [
        ['callable' => 'menu.default_tree_manipulators:checkAccess'],
        ['callable' => 'menu.default_tree_manipulators:generateIndexAndSort'],
    ];
    $tree = $this->menuLinkTree->transform($tree, $manipulators);
    $tree = $this->menuLinkTree->build($tree);
    if (!isset($tree["#items"])) {
      return $variables;
    }
    if (isset($tree["#cache"])) {
      $variables["#cache"] = array_merge($variables["#cache"] ?? [], $tree["#cache"]);
    }
    $variables[$variable] = LinksSettingType::normalize($tree["#items"]);
    return $variables;
  }

once again, ike the links settings type, but simple.

Let's wait the work is merged on USWDS before borrowing.

"Footer top" done.

Do we do "Footer Menu" ?

finally, we don't do footer_menu