fix(container): use scoped binding for parser

[danielebarbaro]

Problem

KmlParserServiceProvider registers KmlParser as a singleton, but the parser holds the loaded document as mutable instance state (protected ?SimpleXMLElement $xml).

Under Octane, or inside a long running queue worker, the container is reused across requests/jobs. That means:

1. Request A calls KmlParser::loadFromFile('customer-a.kml').
2. Request B resolves the same instance and calls getPlacemarks() without loading anything.
3. Request B silently receives request A's data instead of the expected No KML data loaded exception.

Cross-request data leakage, and it fails open (returns wrong data) rather than erroring. Note that phpstan.neon.dist already sets checkOctaneCompatibility: true; static analysis does not catch this class of stateful-singleton issue.

Fix

Swap singleton() for scoped(). A scoped binding behaves exactly like a singleton for the duration of a request or job, so the chained facade usage documented in the README keeps working:

KmlParser::loadFromFile('path/to/file.kml')->getPlacemarks();

but the container flushes it between lifecycles, so nothing carries over.

Tests

Three tests in tests/ServiceProviderTest.php, the third one being the actual regression test (it fails on main):

• the instance is reused within a single scope
• a fresh instance is resolved after forgetScopedInstances()
• a document loaded before the flush is no longer readable after it

Notes

• No breaking change for the usage patterns shown in the README.
• vendor/bin/pint --test currently reports src/KmlParser.php as unformatted on main already. Untouched here to keep the diff focused.