fix: Improve navigation and movement looping behavior

[gonfunko]

The basics

• I validated my changes

The details

Resolves

• Fixes [v13.0.0-beta.0] Workspace position for blocks with constrained move positions #9706
• Fixes [v13.0.0-beta.0] Keyboard looping configuration #9707

Proposed Changes

This PR makes several improvements around keyboard-driven movement and navigation:

• Looping now defaults to on
• The prompt to try unconstrained move mode when a block is moved to the workspace as a top-level block in constrained mode is now only shown once per session
• When blocks are moved to top-level blocks during constrained mode, their position is offset from their prior position to make it clearer that the proposed drop location/state has changed
• Constrained move mode now respects the keyboard navigation looping setting

[maribethb]

I think it is worth thinking through if there is a possible better approach to handle adding the workspace as a "stop" in constrained move, since it has added complexity here. But if you think about it and don't have any better ideas, this LGTM.