feat: add support for viewing completed tasks

[k-vasiliev]

This PR adds basic support for viewing completed tasks. Users can now:

• View completed tasks with viewCompleted: true parameter
• Filter completed tasks by date range using completedSince and completedUntil
• Limit the number of completed tasks shown with completedLimit
• Auto-refresh completed task queries with a minimum interval of 9 seconds due to sync API rate limits

[k-vasiliev]

resolves #233

[aamnakhan]

yay looking forward to this!

[k-vasiliev]

For now, it supports only the title and description of the task.

Also, the sync API returns labels in the "content" field, so tasks with labels look like this:

[k-vasiliev]

@jamiebrynes7 could you take a look?

[jamiebrynes7]

This is really awesome! I mostly have questions around how this is exposed to end-users and trying to resolve some of the confusion that this is introducing inside the query syntax

[jamiebrynes7]

Can we debug log the RequestParams that gets passed into fetcher.fetch like what happens in do?

[jamiebrynes7]

Shall we include the makeUnknownProject call here like with section/labels?

[jamiebrynes7]

We are using the completed task's completed_at for this, so I think this doesn't need to be made optional

[jamiebrynes7]

I think it would be cleaner and clearer if the completed tasks were modelled as a new kind of query block with their own dedicated query schema.

To query for active tasks

```todoist
description: "Today's tasks"
filter: "today"
```

To query for completed tasks (note we can also drop the prefix as its now redundant!):

```todoist-completed
limit: 100
since: 2025-02-01
```

Rather than trying to encode the combinations in the schema here, having two independent schemas (which can still share common elements where applicable!) seems like the best way forward. It also resolves ambiguities like:

• completedLimit/completedSince/completedUntil are meaningless if filter is provided
• sorting/groupBy do not look like they are supported for completed tasks

[jamiebrynes7]

This looks like a call to the completed tasks API endpoint counts as a 'full sync' operation:

For each user, you can make a maximum of 1000 partial sync requests within a 15 minute period.

For each user, you can make a maximum of 100 full sync requests within a 15 minute period.

Is this being conservative or have you verified which kind this request counts as?

Its also worth noting the utility of this is somewhat lessened since a user can have any number of blocks rendered at once

[josemichaelrubio]

This feature will be a clutch for periodic reviews! Anyway, can I contribute to this via development?

[blankster]

To everyone involved, thanks to all who are working on this 🫡 —that's something I've always wanted. 🙏

It's one thing to know what still needs to be done, but the list is often long, even when you narrow your perspective. What personally gives me the strength to do more of what I set out to do when I procrastinate is being able to clearly see what I've already accomplished, because that's something we often forget. I combine this with Habitica as additional gamification to not only feel a sense of completion but also receive direct feedback. Simply being aware of the often large list of things I've done motivates me a lot.

Ideally, this would be grouped in a hierarchical project view so it can be integrated into the daily note. Together with personal notes and other items, it would fit in perfectly.