Bug: create_service_dependencies() filter providers collide when two filtered bundles are merged

[yuuuxt]

Description

Please find all the details in the repo (repo created with AI assisted).

URL to code causing the issue

https://github.com/yuuuxt/advanced_alchemy_filter_dependency_collision

MCVE

# Your MCVE code here

Steps to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

"In the format of: ![SCREENSHOT_DESCRIPTION](SCREENSHOT_LINK.png)"

Logs

Package Version

advanced-alchemy==1.9.3
litestar==2.21.1

Platform

• Linux
• Mac
• Windows
• Other (Please specify in the description above)

[ragbendra]

Hi, I'd like to take this one.

Dug into the repro repo and the filter-provider source, looks like create_service_dependencies() uses fixed key names for the filter providers (search_filter, limit_offset_filter, filters, probably id_filter too), so when you merge two bundles with ' | ' the second one just clobbers the first's entries.

Before I write anything, quick question on direction: namespacing those keys would fix it properly but changes the default param names for people using a single bundle, which could break existing setups. Raising an exception on collision instead wouldn't fix the actual use case but at least stops it failing silently. I could do the exception now as a stopgap and namespace as a follow-up, or just go straight for namespacing if you're fine with the breaking change. Let me know and I'll get a regression test up first either way.