* [maven-release-plugin] prepare release v9.5.0
* [maven-release-plugin] prepare for next development iteration
* Create changes-9.5.0.md
* Set changes.md for 9.6.0
## Conclusion
1. In matching the first rule scenario, the new implementation(mostly due to split performance), it is 40% fast than the previous implementation.
2. Quick match has a huge advantage in GC(time and cost) and memory cost(alloc, G1 Eden and G1 Old) in every case. In my 64G M1 Max env, the regex matching even causes full GC just in the benchmark, which is only running in 2:11 mins. The regex would be a disaster for product env memory.
3. The quick match only has lower performance when the number of pattern rules is less than 4, which is nearly impossible. Even for that, Regex matching costs most GC and memory alloc in a one-time match, and 3-time cost in 4 times match.
## Other Changes
1. I made the URI cache only works in AI pipeline works, as it should. This was a bug in the previous commit.
2. `/` is not required in this case, as generally, the pattern recognition should work well for the demo name as well.
* Support HTTP URI formatting through ai-pipeline to do pattern recognition.
* Add new HTTP URI grouping engine with benchmark.
* [Breaking Change] Use the new HTTP URI grouping engine to replace the old regex based mechanism.
kezhenxu94
Superskyyy
吴晟 Wu Sheng
liuzc9
mrproliu
Kirs