resilience: prove spring-boot-starter-aop was renamed to spring-boot-starter-aspectj, not removed

Maven Central's maven-metadata.xml for both artifact IDs, read together, shows aop's last
release is 4.0.0-M2 and aspectj's first release is 4.0.0-M3 -- a rename at a milestone
boundary, not a drop. The renamed starter's own published POM depends on exactly
spring-aop + aspectjweaver, the two jars this pom.xml's dependency comment already claimed
were needed; this commit adds the reproducible build-break proof, the metadata/POM evidence,
and a new doc chapter, and backs the corrected companion-repo links from the resilience4j-
circuit-breaker-spring-boot post.

resilience/broken-example/pom.xml

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- NOT part of the main build (no parent module lists this directory). Exists only so
+     scripts/reproduce-starter-aop-break.sh can run `mvn compile` against it and capture
+     the real error. See docs/01-two-resilience-stacks.md. -->
+<project xmlns="http://maven.apache.org/POM/4.0.0">
+  <modelVersion>4.0.0</modelVersion>
+  <parent>
+    <groupId>org.springframework.boot</groupId>
+    <artifactId>spring-boot-starter-parent</artifactId>
+    <version>4.1.1</version>
+    <relativePath/>
+  </parent>
+  <groupId>com.ankurm</groupId>
+  <artifactId>break-demo</artifactId>
+  <version>1.0.0</version>
+  <dependencies>
+    <!-- This is the dependency every pre-Boot-4 Resilience4j guide tells you to add.
+         It no longer exists past 4.0.0-M2. -->
+    <dependency>
+      <groupId>org.springframework.boot</groupId>
+      <artifactId>spring-boot-starter-aop</artifactId>
+    </dependency>
+  </dependencies>
+</project>