#5520: drop redundant same-package +alias metas after auto-homing

[morphqdd]

Closes #5520.

Since #5425 the compiler auto-homes a bare reference to an object in the same package, so a hand-written +alias <pkg>.<name> whose <pkg> equals the file's own +package is dead weight. This removes all of them.

For every .eo file that has a +package P meta, the +alias P.<name> lines are deleted, and every cross-package alias is left untouched. For example string/at.eo loses +alias string.slice and +alias string.sprintf (both same-package), while tuple/reduced.eo loses +alias tuple.list and +alias tuple.reducedi but keeps +alias string.sprintf. Root-package files like string.eo keep their +alias string.sprintf because their package is not string.

100 aliases removed across 62 files, pure deletion, no other changes:
string 31, tuple 35, io 17, sm 9, fs 8.

Verification: mvn -pl eo-runtime clean install reaches the Java compilation stage, which means register, parse, assemble, lint and transpile all pass with the aliases gone, so every bare reference still resolves via auto-homing (the lint stage would flag any unresolved reference).

[github-actions]

⚠️ Benchmark Comparison Unavailable

Unfortunately, one of the benchmarks is missing, and we couldn't generate a performance comparison report.

Please ensure that both the base and PR benchmark results are available for analysis.

[morphqdd]

@yegor256, please take a look when you have a moment. All 25 checks are green.

[yegor256]

@morphqdd conflicts here, please resolve them

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud