docs(core): aspects with same priority are not guaranteed to be execu…

…ted in the same order (aws#33596)

document that we don't guarantee the same order for aspects with the same priority level.

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

packages/aws-cdk-lib/core/README.md

@@ -1694,7 +1694,10 @@ values must be non-negative integers, where a higher number means the Aspect wil
 
 By default, newly created nodes always inherit aspects. Priorities are mainly for ordering between mutating aspects on the construct tree.
 
-CDK provides standard priority values for mutating and readonly aspects to help ensure consistency across different construct libraries:
+CDK provides standard priority values for mutating and readonly aspects to help ensure consistency across different construct libraries.
+Note that Aspects that have same priority value are not guaranteed to be executed
+in a consistent order.
+
 
 ```ts
 /**

packages/aws-cdk-lib/core/lib/aspect.ts

@@ -40,7 +40,10 @@ export interface AspectOptions {
    * The priority value to apply on an Aspect.
    * Priority must be a non-negative integer.
    *
-   * @default - AspectPriority.DEFAULT
+   * Aspects that have same priority value are not guaranteed to be
+   * executed in a consistent order.
+   *
+   * @default AspectPriority.DEFAULT
    */
   readonly priority?: number;
 }