docs: Clarify input transformation support for EventBridge Pipes (#287)

Author: HarshCasper

src/content/docs/aws/services/pipes.mdx

@@ -198,11 +198,12 @@ or Amazon S3 logs.
 
 The EventBridge Pipes implementation in LocalStack is currently in preview stage and has the following limitations:
 
-* Lack of input transformers.
-* Lack of concurrency support (i.e., ParallelizationFactor), resulting in slower processing in high-throughput scenarios.
-* Lack of lifecycle management for pipe states (i.e., missing tests for state transitions).
-* Lack of re-sharding support when polling from Kinesis and DynamoDB streams.
-* Batch handling behavior may have parity issues (e.g., batch flushing rules by size, length, time, etc. are not implemented).
+- Input transformation is supported **for targets only**. Enrichment input transformation is not yet available.
+- Support for wildcards (`*`) in JSONPath in input transformation is not implemented.
+- Lack of concurrency support (i.e., ParallelizationFactor), resulting in slower processing in high-throughput scenarios.
+- Lack of lifecycle management for pipe states (i.e., missing tests for state transitions).
+- Lack of re-sharding support when polling from Kinesis and DynamoDB streams.
+- Batch handling behavior may have parity issues (e.g., batch flushing rules by size, length, time, etc. are not implemented).
 
 ## API Coverage