fix: add missing 'effectivePlatformFeatures', 'createdAt', 'isPaying' to User interface

[metalwarrior665]

Prerequisite apify/apify-docs#1569 was merged

Questions:

1. The string -> Date conversion happens automatically for all types, right? So no need to do anything?
2. Do we use explicit T | null anywhere if the API returns the type or null? Seems we like to do T? rather

[B4nan]

The string -> Date conversion happens automatically for all types, right? So no need to do anything?

I believe it works automatically on keys suffixed with At, so createdAt should work fine. Best way to be sure is to write a test case (or at least try it out locally with the changes).

Do we use explicit T | null anywhere if the API returns the type or null? Seems we like to do T? rather

I personally prefer using optional fields (so undefined) for better ergonomics, but if the API returns null somewhere, we need to have it in the type, and if a user can pass null somewhere explicitly, we need to allow it in that type too.

[B4nan]

looks good, but please ensure the nulls are correct (so if the API can return null somewhere, we have it on type level, if not and the API would instead omit the property, it shouldn't be there)

[metalwarrior665]

I tested the Date conversion locally and double-checked the explicit nulls