Unsafe fall-through in getWhereConditions
### Impact
Providing an invalid value to the `where` option of a query caused Sequelize to ignore that option instead of throwing an error.
A finder call like the following did not throw an error:
```ts
User.findAll({
where: new Date(),
});
```
As this option is typically used with plain javascript objects, be aware that this only happens at the top level of this option.
### Patches
This issue has been patched in `sequelize@6.28.1`
https://github.com/sequelize/sequelize/pull/15699 & `@sequelize/core@7.0.0.alpha-20`
https://github.com/sequelize/sequelize/pull/15375
### References
A discussion thread about this issue is open at
https://github.com/sequelize/sequelize/discussions/15698
CVE: CVE-2023-22579
Snyk:
https://security.snyk.io/vuln/SNYK-JS-SEQUELIZE-3324090