fix(dynamicpathdetector): include Internal in endpoint merge key

[entlein]

HTTPEndpoint.Equal distinguishes endpoints by (Endpoint, Direction, Internal), but MergeDuplicateEndpoints was keying only on (Endpoint, Direction). Three places leaked the bug:

1. getEndpointKey — duplicate-detection at the top of the loop would collapse two endpoints that differ only in Internal.
2. The wildcard-after-specific sweep — a :0/x Internal=false wildcard could absorb a previously-recorded :443/x Internal=true sibling because the sweep only checked path + direction.
3. The wildcardKey lookup for specific-after-wildcard ordering — same omission, so a specific-port entry could fold into a wildcard with a different Internal.

Result: profile entries that the runtime semantically considers distinct (Internal=true vs false) were silently merged into one, losing the internal/external distinction for that path.

Fix: include Internal in getEndpointKey, the sweep predicate, and wildcardKey, all keyed identically so the map lookups stay consistent.

4 new regression tests pin all three spots plus a positive sanity check that matching-Internal merges still happen. Existing tests unchanged.

Flagged on upstream review of kubescape#316.

Sorry, we do not accept changes directly against this repository. Please see
CONTRIBUTING.md for information on where and how to contribute instead.

[github-actions]

Summary:

• License scan: failure
• Credentials scan: skipped
• Vulnerabilities scan: skipped
• Unit test: success
• Go linting: failure