[browser] Fix processing of satellite assemblies from referenced assembly during publish

[maraf]

• Fix computation of RelatedAsset to satellite assemblies from <Reference />.
• Explicitly pass ResolveAssemblyReferencesFindRelatedSatellites=true to nested publish to enable searching for satellite assemblies.
• WBT for satellite assemblies with <ProjectReference /> & <Reference />.

Context

• We need to read list of assemblies from nested publish because IL-stripping is not in place (it produces assemblies at a different location).
• The nested build (in common targets) ResolveAssemblyReferencesFindRelatedSatellites is set to false by default

Fixes #105937

[maraf]

This AOT failure didn't find app assembly AOT module. Based on output it seems it didn't run main (out it didn't provide console writes), but return of 42 from nodejs is expected https://helix.dot.net/api/2019-06-17/jobs/61a94806-100b-49f2-b546-f69dd33afd15/workitems/Workloads-NoWebcil-ST-Wasm.Build.Tests.WasmTemplateTests/console
EDIT: It doesn't fail the same locally in Debug not Release
EDIT2: Seems like just one hit, rerun didn't show it again

[maraf]

What if the main assembly gets linked out, but we add satellites for it?

In console app published trimmed, it copies all satellite assemblies, even for linked out libraries

[maraf]

/backport to release/9.0

[github-actions]

Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/10720328255