Revert to previous target creation logic

Fixes #1576 #1577

fix(allocator): Set --enable-unsafe-swiftshader with --disable-gpu

In Chromium 139+, falling back to Swiftshader will be opt in:

https://chromestatus.com/feature/5166674414927872

This means that anything currently leveraging DisableGPU in chromedp
will fail to fallback in the future without this flag set

This is already current behavior in upstream builds of Chromium 138

This sets --enable-unsafe-swiftshader to retain existing behavior and
prevent regressions in anything using chromedp

Signed-off-by: RJ Sampson <rj.sampson@chainguard.dev>

Fixing issue with page.Navigate calls

allocator: fix race that causes workgroup panic

`readOutput`'s copy goroutine was able to race with the ws read timeout
resulting in a panic

fixes by moving the copy task after we return the `wsURL` and no longer
can go into the timeout case

while at it, fixes an unrelated data race that `err` could have been
written to by `readOutput` and the wsURL read timeout case

Fix CreateTarget call

fix: #1448

Updating cdproto

add tests for unmarshalling and marshalling json

Allow setting jsonv2 Marshal/Unmarshal options

fix: add page.EventFrameStartedNavigating to ignored events (Google C…

…hrome 134.x)