Xsdjam ratelimit - fixing broken jmeter regression tests

The assert for unique uri-regex + http-methods was not quite right and the jmeter configs had a permutation that failed to validate with the initially designed assert.

This change still does not do 100% validation of the scenario we want, but should not cause false validation failures.

Also, refactored the schema unit test to include the xml config samples inline (remove overhead of a config resources directory for test).

Manually verified that the rate-limiting configs in the automation (jmeter) directory all validated against the latest rate limit schema.  Had 1 failure which is likely due to the config no longer being used.  Updated the config to ensure it will validate if it does get used.