Support navigation module

I don't think we can ship that config change as part of the Dashboard module.

Would be great if we could get ✨ Provide Config Action to add new blocks to navigation from recipes Active merged to allow to include the dashboard block as part of the corresponding Drupal CMS recipe. Another option would be to add the block to the navigation top programmatically, following the approach in ✨ Allow modules to hook into top of content/footer sections of new core navigation Active .

Regarding the hook implementation, 📌 Provide a way for other modules to flag block plugin implementations as 'navigation safe' Active should be taken into account as well.

Created ✨ Mark navigation dashboard block as navigation safe Active after 📌 Provide a way for other modules to flag block plugin implementations as 'navigation safe' Active landed for the Drupal CMS use case.
I'd like to focus this issue on how to provide the block by default in any site with Navigation + Dashboard enabled.

For Drupal CMS this shouldn't be a blocker, as we can provide the config there or use the config action when it lands in the recipe.

This is postponed on ✨ Provide Config Action to add new blocks to navigation from recipes Active landing.

I discussed this today with @plopesc. From all the alternatives, we have, my preference is still using the block.
We would need to implement hook_install (for adding the block), hook_uninstall (for removing the block), and hook_modules_installed (in case navigation is enabled AFTER dashboard).

Before we work on this, we should wait for ✨ Allow other modules to include their own Navigation blocks during installation Active .
If that lands it would simplify a ton the work needed for this.
If it doesn't, we should use that MR code as a reference.