tests: enable bundled_core and bundled_lua e2e fixtures

[argonui]

What

Removes bundled_core and bundled_lua from the deny list in tests/e2e_test.go so the two bundling fixtures get real end-to-end round-trip coverage.

Fixes #101

Why the deny list was there — and why it was wrong

The deny-list comment claimed both fixtures "depend on a src file that the test doesn't know about." That turns out to be inaccurate. Both bundles are self-contained: the module bodies are inlined in the fixture. On reverse, the harness unbundles each script's modules to src/ (via LuaSrcWriter); on build, require() is resolved back in from the same in-memory filesystem. No external src fixture is needed.

• bundled_core (root-level bundled script requiring core/Global) passes as-is once un-denied.
• bundled_lua nests its bundled script inside an ObjectStates entry, where the savegame is compared byte-for-byte. Genuine luabundle 1.6.0 output preserves a module's trailing newline that the unbundle → re-bundle round trip normalizes away, so the comparison fails on trailing-whitespace formatting alone — not on any missing module or wrong content.

The fix

The harness already sidesteps bundling's formatting-sensitivity for the top-level LuaScript by comparing it as a set of module names rather than bytes. This generalizes that same, already-documented rule to bundled scripts at any nesting depth, so a nested object script is held to the same standard as the root.

• Only IsBundled scripts are normalized; non-bundled object scripts are still compared exactly, so no existing fixture's coverage is weakened. bundled_lua is the only fixture with a nested bundled script, so nothing else changes behavior.
• Docs in tests/AGENTS.md and bundler/AGENTS.md updated to match.

Testing

go build ./... && go vet ./... && go test ./... all green, with bundled_core and bundled_lua now running (confirmed via -v) and passing.