Bubble or at least log Navigation Aborted Errors to Client

Describe the bug

Navigation Aborted errors do not get bubbled up to the client, see my discussion here on what I went through to discover this.

https://github.com/sveltejs/kit/discussions/13777

Needless to say I would of save a great deal of time if it bubbled up the error message, as it took me an exceptionally long time to even realize it was a Navigation Aborted error in the first place. Then the number of things that can actually cause this problem are numerous and not well documented at all, the error it throws has absolutely zero information that is of any help when this happens as well. It's an exceptionally easy problem to get yourself into especially with reactive systems we build today, and an exceptionally hard problem to find with the way it's currently being treated.

Reproduction

Have a DOM event occur in the background while a navigation event occurs using goto, it will just sit there and do nothing. No error is thrown.

Logs

System Info

Svelte 4.x, SvelteKit 2.x 

(latest minors on all)

Severity

serious, but I can work around it

Additional Information

No response

Start by reading the linked discussion #13777 and reproducing the reported interaction: a DOM event occurring while goto navigation is in progress. Trace where the navigation-aborted condition is handled in the client navigation flow. Done means the client receives or logs useful information instead of silently appearing to do nothing, with coverage for the reported reproduction.