bugfix: only allow results that are within specified season/year and nulls

[irfan-dahir]

Issue/Discussion: https://discord.com/channels/460491088004907029/1119461866322800662

There are a handful of entries like 52991 start on September 29th which is technically in the range of the summer season (which is why it returns in the results for summer 2023). However, it's officially listed under the Fall season in premiered.

---

This PR attempts to resolve this issue by filtering down the results to

1. It contains the premiered string (e.g "Summer 2023") from a specific seasonal endpoint request
2. It contains null values (for OVA, ONA, Movie, etc that have premiered set to null)
3. It contains entries within the range given by the current season's start_date and end_date (Existing behavior)

[pushrbx]

I tried to add my comments in top down order, so you would read them after each other and they are connected.

In summary:

• getSeasonItems function of QueryAnimeSeasonHandlerBase class should not change
• getAiredBetween function in AnimeRepository class should handle the edge case if "premiered" date should always take precedence. Ideally this function should have the business logic to handle the situation. I would also add a new function maybe with the arguments you added, which wraps around getAiredBetween and adds the extra filters based on premiered, if it's possible to override the query builder that way. (haven't checked yet)
• Existing behaviour of resolving season based on date, and the current way of resolving request params to a date range should remain as is. We would want to deal with the inconsistency at the database query level: if request was for season:spring year:2023
  then the query should first consider the premiered string then the aired date range based on the resolved date range.

[irfan-dahir]

@pushrbx

I would also add a new function maybe with the arguments you added, which wraps around getAiredBetween and adds the extra filters based on premiered, if it's possible to override the query builder that way. (haven't checked yet)

I tested this but getAiredBetween returns with the orderBy query afterwards, so any added query does not work.

So I added premiered as an argument for getAiredBetween and it handles the logic inside it instead. Let me know if that works here?

[pushrbx]

Now it looks ok.