Release b326

fix: trigger fallback on 404/422 model not found errors

Previously, when a backend returned 404/422 (e.g., 'model does not exist'),
the gateway treated it as a client error and didn't attempt fallback to
other matching backends. Now it will retry with fallback clients for
404/422 errors.