Fix override of legacy resource providers over new community ones for certain resources

[dominikschubert]

Motivation

After #10242 the -ext pipeline started failing.

I unfortunately missed an edge case where we previously had legacy providers in both community and -ext (-ext providers with additional features) but now only have a new provider in community and no new one in -ext yet.

What needs to happen is that for those 3 resource types, if PRO is enabled, the legacy model from -ext is used. With the recently introduced logic it was falling back to the community provider before considering the legacy models though.

Changes

• Until we have corresponding resource providers for these 3 resource types in -ext, I've added a manual exemption list in community. Will refactor this soon though, so this is just a temporary inconvenience.

[coveralls]

coverage: 83.864% (-0.01%) from 83.878%
when pulling 1b73439 on hotfix-cfn-legacy-fallback
into f3ddfc9 on master.

[github-actions]

LocalStack Community integration with Pro

    2 files  ±0      2 suites  ±0   1h 21m 24s ⏱️ +24s
2 641 tests ±0  2 394 ✅ ±0  247 💤 ±0  0 ❌ ±0 
2 643 runs  ±0  2 394 ✅ ±0  249 💤 ±0  0 ❌ ±0 

Results for commit 1b73439. ± Comparison against base commit f3ddfc9c.

[dominikschubert]

Manual -ext run with this branch was green, so going ahead with the merge to unblock the -ext pipeline.