fix(build-cli): Use correct line endings

[tylerbutler]

Fixes the generate:packlist and check:layers --md commands to output files using LF line endings regardless of platform.

[Copilot]

Pull Request Overview

This PR fixes the CLI build commands to enforce consistent LF line endings across generated files regardless of the platform.

• Introduces a new helper function writeFileWithLineFeeds in text.ts to normalize CRLF to LF.
• Updates generate:packlist and check:layers --md commands to utilize writeFileWithLineFeeds.
• Removes reliance on OS-specific EOL defaults by hardcoding LF.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
build-tools/packages/build-cli/src/library/text.ts	Adds a helper to write files with LF line endings
build-tools/packages/build-cli/src/library/layerGraph.ts	Replaces OS EOL with LF as the repo standard
build-tools/packages/build-cli/src/commands/generate/packlist.ts	Updates packlist command to write consistent LF output
build-tools/packages/build-cli/src/commands/check/layers.ts	Updates layers command to use writeFileWithLineFeeds for LF output

[steffenloesch]

I've tried running a build off the branch locally on my machine, and I seem to be getting even more touched files than before:

I did pnpm clean before running the build, and I had reverted all local changes.

[tylerbutler]

I've tried running a build off the branch locally on my machine, and I seem to be getting even more touched files than before:
...
I did pnpm clean before running the build, and I had reverted all local changes.

When you tested, did you link the local copy of build-tools to the root workspace? See https://github.com/microsoft/FluidFramework/tree/main/build-tools#testing-build-tools-changes-in-the-client-release-group. That step is needed to test since we pin the version of build-tools used in the client release group to a specific version.

[steffenloesch]

I've tried running a build off the branch locally on my machine, and I seem to be getting even more touched files than before:
...
I did pnpm clean before running the build, and I had reverted all local changes.

When you tested, did you link the local copy of build-tools to the root workspace? See https://github.com/microsoft/FluidFramework/tree/main/build-tools#testing-build-tools-changes-in-the-client-release-group. That step is needed to test since we pin the version of build-tools used in the client release group to a specific version.

No I did not. Will try. Thanks for the context!