Make "Place navigation block" a primary button and move it right before the table

@rkoller first, thanks for taking the time to review this! :D

Getting into your proposal, I don't think I agree with it. This is why:

First, we already have the primary button for the form at the end of the form. And that's my main reason for it.

Functionally it not really belongs there, since for one it is no draggable menu/navigation block plus it has less affordance through the close proximity to the table header in lighter grey.

It actually is a draggable area :) Plus I think it does belong there because it's the tool that you need to add more items to that specific table/list of elements. About the "it has less affordance through the close proximity to the table header in lighter grey", I do agree but that's more a design problem with the grey regular buttons we'll hopefully solve with the new designs from 📌 [META] Implement the final design system Fixed (and hopefully we get rid of the 50 shades of gray :D).

Anyway, happy to keep discussing this if you don't agree :)

thank you for explaining your points! and yes I disagree in this case, but i will try illustrate my arguments with a few screenshots (something i should have already done in my initial issue summary).

First in regards of the primary button. There are several examples across the admin ui that have two primary buttons, one to save the configuration form and one for adding something. Two examples are:

Both have a primary add button adding an object to the draggable area underneath. The suggestion making the button a primary button was mainly due to consistency reasons since more or less all add buttons across the admin ui are blue primary buttons.

And in regards of the draggable area i meant the following. The block layout page is sort of a special case from my perspective. one of the very few cases where it makes "sort of" sense to have some kind of "section headers" within the block list containing each the label for the block region and the place block button, which provides the convenience that the block is directly placed into the block region the button is pressed. but these highlighted block region rows are in contrast to the other rows not draggable (they even miss a drag handle):

Same for the row on the navigation blocks page, that row with just the place navigation block button is also not draggable but in contrast to the block layout page it doesn't contain any sections. That is the reason why i've thought it would make sense to move the place navigation block button out of that table. it just feels out of place there.

One compromise might be to move the button out of the table but instead of making it a blue primary button keep it as a grey regular button? but as i said the suggestion making it a blue primary button was based on consistency reasons.

saw in todays ux meeting that the navigation blocks page changed to a layout builder based approach. so i close this as outdated.