Add withMutes=1 option to MastoAPI post-returning endpoints
The idea is so that if FE or client wants to, they can process muted statuses themselves. I.e. PleromaFE would collapse them with option of removing them completely. This would solve the discrepancy between MastoAPI/Clients "nuclear" mutes and PleromaFE/Qvitter "non-extrimist" mutes.