Add User.recently_active scope

[mjankowski]

Changes:

• In usage outside the User-class (one in feed manager, two in account interactions) merge in the scope instead of repeating the query conditions.
• In the User class itself -- an existing active scope was also repeating this logic, so replace it with the new scope.
• While in there, update inactive to match style of new scope since they are opposites

I believe this brings all references to the active duration constant back into User class. Other than changed quoting on the generated queries from the framework, the generated sql for the existing usage is the same.

Possible future thing here -- I did not look at how much usage of the existing active scope there is. The name here is sort of misleading, but something like confirmed_and_recently_active_and_account_not_suspended is excessive. Maybe there's a better alternative.

[mjankowski]

Closing in favor of #29775