Reduce qualified type and event names

[leighmcculloch]

Note

Part of a stack of PRs that must merge in this order.

A first group of PRs change contract specs so that they are produced at compile time instead of at proc-macro execution time. This provides the foundation to construct the specs from information that is only known at compile time, like the fully qualified name of a type:

1. Add borrowed View variants of types rs-stellar-xdr#560
2. Add const XDR serialization rs-stellar-xdr#562
3. Encode contract spec XDR at compile time rs-soroban-sdk#1965

A second group of PRs changes the type names that the sdk stores in specs are fully qualified type names, and then the cli reduces them down to unique simple identifiers. During the contract build the types are given names like ::mycrate::mymod::MyType instead of MyType. Then the cli reduces them back down to simple names after spec shaking. Qualified type names make it possible to uniquely identify types in the spec, even when they have the same name. This resolves several problems with contract specs the type identify problem (stellar/rs-soroban-sdk#1570), type aliases limitations (stellar/rs-soroban-sdk#1857 stellar/rs-soroban-sdk#1063), and optimise spec shaking data section size (stellar/rs-soroban-sdk#1978):

1. Widen contract spec type and event name limits stellar-xdr#312
2. Widen contract spec type and event name limits rs-stellar-xdr#566
3. Qualify type and event names rs-soroban-sdk#1970
4. Reduce qualified type and event names #2674 ← this PR

Note that downstream clients and SDKs should see no, or little, change because the cli will during the build process reduce the fully qualified names back to simple unique names. Contracts that had colliding type names, which meant they could not be used with clients, will now work.

A third group of PRs are an optimisation to spec shaking v2, and will use the new unique type names to shake type specs by reachability, producing a dependency graph (thanks @mootz12), so that only spec entries that can't be reached from fns, like errors and events, get spec markers from dead-code-elimination:

1. Shake specs by reachability and markers rs-soroban-sdk#2043
2. Announce spec shaking v3 and shake by the recorded version #2720

What

Patch stellar-xdr to stellar/rs-stellar-xdr#566 so the CLI can read the widened user-defined type name limit (exposed as SC_SPEC_TYPE_NAME_LIMIT, which the hardcoded StringM<60> sizes now reference), and reduce the fully qualified UDT type names that stellar/rs-soroban-sdk#1970 emits (e.g. my_contract::inner::State) down to short names in contract info interface output, disambiguating name collisions with numeric suffixes and reporting every rename and collision.

Why

Contract specs are moving to fully qualified user-defined type names, whose :: separators are not valid identifiers, so the Rust and JSON renderers cannot use them verbatim; the CLI has to shorten them for display and code generation, and warn when distinct qualified types reduce to the same short name.

Known limitations

Depends on stellar/rs-stellar-xdr#566 landing and releasing, after which the [patch.crates-io] git revision is replaced with a published version. The soroban-sdk qualified-name change (stellar/rs-soroban-sdk#1970) is not patched into the workspace: it is still on the 27.0.5 line and lacks the protocol-28 SDK APIs the repo's test contracts now use, and the CLI only needs xdr #566 to read the widened names, so the reduction runs CLI-side on any spec.