Collect executables from modules generated by macro calls

[integraledelebesgue]

Unitl now, find_executable_function_ids would skip modules generated by calling declarative macros on a top level (ModuleId::MacroCall). In particular, it disallowed generating Forge tests using declarative macros

[reviewable-StarkWare]

This change is 

[cursor]

PR Summary

Low Risk
Narrow change to executable discovery with an added test; no auth or data paths, though macro-expanded executables could slightly widen what gets compiled as entry points.

Overview
Executable discovery now walks the same module graph as semantic caching, so #[executable]-style functions emitted inside declarative macro expansions are no longer skipped.

find_executable_function_ids replaces db.crate_modules with all_crate_modules_for_cache, which follows submodule and macro-call module edges (e.g. top-level make_executable!()). That unblocks patterns like Forge tests defined via macros. A compiler integration test asserts an executable inside a macro-generated module is collected under the mock "some" attribute.

^{Reviewed by Cursor Bugbot for commit c55309e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[orizi]

@orizi reviewed 2 files and all commit messages, and made 1 comment.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on integraledelebesgue).