Don't warn in recursive context settings toProxy

[maraisr]

Currently Im putting a playwright Browser and Page instances onto the context in a .before into a context:

myTest.before(async (context) => {
        context.browser = await chromium.launch({
		headless: false,
	});
	const browsingContext = await context.browser.newContext({
		bypassCSP: true,
	});
	context.page = await browsingContext.newPage();
});

and then later reading that like:

myTest('open's website', async (context) => {
	await context.page.goto(context.baseUrl); // Note this comes statically when I created the `suite`.
	assert.ok(/test for something/.test((await context.page.content())));
});

but this seems to mutate the page object in someway—probably Playwright internals. And for this my console is littered with:

[WARN] Cannot modify context within tests!

---

My plan is to still echo that these objects should be immutable but perhaps only on key? Or a config to say "i know what im doing", as I assume these need to stay immutable so tests could be ran in parallel in the future? (but on that, with e2e's you'd want them in-series).

[lukeed]

There's some related discussion in #39 which steers me towards completely removing the "immutability guard" that uvu provides right now. Not doing anything is the simplest approach by far, and I trust users will be aware of what they're doing/modifying