fix: referenced_by compilation on different debug profiles

[Legend-Master]

Closes #13865
Closes #15406

Closes #15603

I don't even know how I thought of this to be honest 🤯

[github-actions]

Package Changes Through 9cb654a

There are 14 changes which include tauri with minor, tauri-cli with minor, @tauri-apps/cli with minor, tauri-bundler with minor, tauri-utils with minor, tauri-build with minor, tauri-macos-sign with minor, tauri-runtime-wry with minor, tauri-runtime with minor, tauri-codegen with minor, tauri-macros with minor, tauri-plugin with minor, tauri-driver with minor, @tauri-apps/api with minor

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
@tauri-apps/api	2.11.1	2.12.0
tauri-utils	2.9.3	2.10.0
tauri-macos-sign	2.3.4	2.4.0
tauri-bundler	2.9.4	2.10.0
tauri-runtime	2.11.3	2.12.0
tauri-runtime-wry	2.11.4	2.12.0
tauri-codegen	2.6.3	2.7.0
tauri-macros	2.6.3	2.7.0
tauri-plugin	2.6.3	2.7.0
tauri-build	2.6.3	2.7.0
tauri	2.11.5	2.12.0
@tauri-apps/cli	2.11.4	2.12.0
tauri-cli	2.11.4	2.12.0
tauri-driver	2.0.6	2.1.0

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[Legend-Master]

Seems like there's still leakage to the final binary...

[Legend-Master]

Well... Did some other hack by removing all the ResolvedCommandReference fields on not #[cfg(debug_assertions)]... This seem to not increase the binary sizes anymore

[FabianLars]

no means to test this rn but lgtm, nice :)

[Legend-Master]

Well, had to do the same for new hack for the ResolvedCommandReference, should be good to go now