Support obfuscating assemblies with missing dependencies (upstream PR #155)

[mcpolo99]

Upstream: mkaring#155

Allows obfuscation even without all transitive dependencies present, making worst-case assumptions for missing ones. Owner's own PR, never merged.
Action: Cherry-pick or adapt PR mkaring#155.

[mcpolo99]

Upstream PR mkaring#155 is from 2020 and changes 215 files — too diverged to cherry-pick. Would need a full reimplementation based on the concept. Deprioritizing to backlog.

[mcpolo99]

Updated Analysis

The upstream PR mkaring#155 (215 files changed, from 2020) is too diverged to cherry-pick. However, our recent fixes significantly reduce the need for this:

1. PR feat(core): auto-detect .NET runtime paths for assembly resolution #55 — Auto-detects .NET runtime paths, resolving most BCL "missing dependency" failures
2. PR fix(protections): ref proxy mild mode skip unresolvable external types #42/fix(protections): skip unresolvable types in ref proxy phase #45 — Ref proxy and ReferenceProxyPhase now skip unresolvable types instead of crashing
3. PR fix(renamer): handle FnPtr type signatures without crashing #43 — FnPtr types handled gracefully instead of throwing

The remaining gap: when obfuscating assemblies with truly missing third-party dependencies (not BCL), ConfuserEx still crashes at the Inspection phase (ResolveThrow on all AssemblyRefs).

A practical fix would be to make the Inspection phase warn-and-continue instead of throw-and-crash for non-critical dependencies. Moving to backlog as a lower priority since the most common cases (BCL resolution, external type references) are now handled.

[mcpolo99]

Merged to pre-release via PR #58.