[performance] add caching of status fave, boost of, in reply to ID lists

[NyaaaWhatsUpDoc]

Description

• updates go-cache library to use more fine-grained zero value detection
• adds caching of status fave, boost of and in reply to ID slices
• adds caching of fetching a boosted status
• updates wipeStatus() to use a multierror, to ensure full wipe

The diff for this ended up shorter than I thought for the amount of work that went in... This PR is only as short as it is as a culmination of other efforts I put into #2049 #2027.

Checklist

• I/we have read the GoToSocial contribution guidelines.
• I/we have discussed the proposed changes already, either in an issue on the repository, or in the Matrix chat.
• I/we have performed a self-review of added code.
• I/we have written code that is legible and maintainable by others.
• I/we have commented the added code, particularly in hard-to-understand areas.
• I/we have made any necessary changes to documentation.
• I/we have added tests that cover new code.
• I/we have run tests and they pass locally with the changes.
• I/we have run go fmt ./... and golangci-lint run.

[tsmethurst]

Looking good!

Just to check, when a new status is put in the database, does it also invalidate the boost IDs and reply IDs cache? Likewise for faves: does a new fave invalidate the faves/likes cache entries for that status ID?

I didn't see it in the code anywhere, so just wanted to verify that that's happening as expected.

[NyaaaWhatsUpDoc]

Looking good!

Just to check, when a new status is put in the database, does it also invalidate the boost IDs and reply IDs cache? Likewise for faves: does a new fave invalidate the faves/likes cache entries for that status ID?

I didn't see it in the code anywhere, so just wanted to verify that that's happening as expected.

When a new status or favourite is put in the database, it's wrapped in the cache.Store() function, which calls all the required invalidate hooks :)

[tsmethurst]

Feel free to squerge when you're happy!