fix(e2e): route exact E.164 Chime DID

[ryanmurf]

Summary

• add a sanitized production-shaped Chime INVITE fixture and strict CRLF/Content-Length validation
• route only the owned literal-plus E.164 DID in the trunk integration config
• prove neighboring DID returns 404 and an untrusted source returns 403
• add a matcher regression showing _X. does not match a leading plus

Verification

• tests/e2e-trunk/run.sh
• python3 tests/e2e-trunk/test_chime_fixture.py
• cargo +1.97.0 test -p asterisk-core test_e164_plus_requires_literal_extension -j8
• shellcheck, bash syntax, clippy, and build checks passed locally

Root cause from the first supervised Chime attempt: the real Request-URI user was +19709601891; the staged _X. dialplan pattern correctly rejected the literal plus and returned 404.