(compat) Update client-utils to auto generate layer compatibility generation

[agarwal-navin]

#25670 added a command (fluid generate layerCompatGeneration) that will auto-generate the layer compatibility generation for packages that support it.

This change leverages that as follows:

• Added layerGeneration:gen script to client-utils's package.json file which will run the above command.
• Ran the script to generate the layer compatibility generation for the client-utils package. It auto-added layerCompatMetadata to its package.json and auto-generated a layerGenerationState.ts file which contains the generation value. The generation is set to 2 since that is the current generation (hard coded in different layers).

AB#51927

[Copilot]

Pull Request Overview

This PR adds layer compatibility generation tracking infrastructure to the codebase. The changes enable automatic generation and updating of layer generation files based on package versions and release dates, with the goal of tracking compatibility across different Fluid layers over time.

• Adds layerGenerationState.ts file to @fluid-internal/client-utils package with generation value of 2
• Introduces layerGeneration:gen npm script and build configuration to auto-generate generation state files
• Updates version setting logic to regenerate layer generation files alongside package version files

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
packages/common/client-utils/src/layerGenerationState.ts	New auto-generated file defining generation constant (value: 2) for layer compatibility tracking
packages/common/client-utils/package.json	Adds layerGeneration:gen script and fluidCompatMetadata with generation 2, release date, and package version
fluidBuild.config.cjs	Adds layerGeneration:gen task configuration and includes it as a dependency of build:docs
build-tools/packages/build-cli/src/library/package.ts	Updates setVersion function to run layerGeneration:gen script during version updates

[agarwal-navin]

Policy check is failing because this line ends with a full stop.
@scottn12 @tylerbutler Not sure if this is intentional but either way, this will need a build-tools change.

[tylerbutler]

You can add an ignore for the policy in the root fluidBuild.config.cjs

[agarwal-navin]

Adding layerGenerationState.ts to policy:handlerExclusions seems to fix the problem. However, I think it might be better to just update the code that generates the file to not have a full stop. What do you think?

[tylerbutler]

Do both. Use a workaround for now, fix build-tools, then integrate the fix and remove the workaround. Assuming you're blocked. If not, you can fix it first.

[agarwal-navin]

Good point. I manually removed the . as a workaround. I should wait to check this PR in until the release happens though. Otherwise, this file might be regenerated and the changes to the build process won't be in creating confusion.