Code Simplification: Removed unnecessary else clause in if statement in AbstractJpaQuery, EqlQueryRenderer, JpaEntityInformationSupport

[chs98412]

Hello! This PR aims to simplify the code by removing the unnecessary else clause in the if statement. While I was looking through AbstractJpaQuery, EqlQueryRender, and JpaEntityInformationSupport, I discovered an unnecessary else syntax and suggested pr similar to before. I think the else clauses can be safely removed without affecting the logic. Your review and feedback on the changes would be greatly appreciated. Thank you!

• [x] You have read the Spring Data contribution guidelines.
• [x] You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• [ ] You submit test cases (unit or integration tests) that back your changes.
• [ ] You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[mp911de]

Thanks for your suggestion. The affected code uses consistently if … if else … else styling and we want to keep it that way.