Keep generated ALC helpers private

[PrzemyslawKlys]

Summary

• keeps PowerForge-generated development binary loader helpers out of FunctionsToExport
• preserves real root-psm1 function export detection for modules that intentionally expose script functions
• adds regression coverage that Desktop binary conflict advisories do not fail staging builds by default

Why

PSWriteOffice's packaged ALC conflict lane was failing after the OfficeIMO release because the generated Import-<ModuleName>DevelopmentBinaryModule helper was being detected as a public function export. Documentation parity then required command docs for that internal helper. Binary conflict scanning itself remains advisory-only: the Desktop advisory is shown, but the build continues.

Validation

• dotnet build .\PSPublishModule.sln --nologo
• dotnet test .\PowerForge.Tests\PowerForge.Tests.csproj --filter "FullyQualifiedName~ModuleBuilderManifestMutatorTests|FullyQualifiedName~ModulePipelineExportAssemblyInferenceTests" --no-build --nologo --verbosity normal
• PSWriteOffice local build using this PSPublishModule DLL completed with documentation parity verified at 421 Markdown / 421 MAML commands
• PSWriteOffice packaged ALC conflict smoke test passed with a default-context DocumentFormat.OpenXml conflict assembly