Describe the bug

Creating a CloudFront Function without specifying name can result in non-deterministic naming when the Node ID is relatively long. This results in unexpected function renames.

Expected Behavior

The method used to create a CloudFront Function name should be deterministic, predicable, and stable.

Current Behavior

The name of Functions is unstable, resulting in resource renames and snapshot failures.

Reproduction Steps

Run the following sample integration test several times. See that eventually it bounces between:

• AReallyLonIdIsAlsoPrettyLongIGuess25040025
• AReallyLoIdIsAlsoPrettyLongIGuess25040025
  for the name of the function.

import * as cdk from 'aws-cdk-lib';
import * as cloudfront from 'aws-cdk-lib/aws-cloudfront';
import * as integ from '@aws-cdk/integ-tests-alpha';

const app = new cdk.App();
const stack = new cdk.Stack(app, 'A-Really-Long-Stack-Name-Example');

const fn = new cloudfront.Function(stack, 'ExampleFunctionIdIsAlsoPrettyLongIGuess', {
  code: cloudfront.FunctionCode.fromInline('function handler(event) { return event.request }'),
});

new integ.IntegTest(app, 'FunctionNameLong', {
  testCases: [stack],
});

Possible Solution

Additional Information/Context

This is also causing the failure on #28571

CDK CLI Version

2.118.0

Framework Version

2.118.0

Node.js Version

v20.2.0

OS

Linux

Language

TypeScript

Language Version

No response

Other information

No response