Consider using a single file-naming scheme and test grouping methodology

Nessuno ha ancora preso questa issue.

Currently, while browsing the test repository, i find it difficult to navigate to tests i expect to exist, and/or not to exist, as the file naming scheme (and test grouping) seems to be all over the place.

I think it'll be worth it (for organisational purposes) to organise files and scope tests such that someone new coming into the repository can find their way and discover related tests better.

---

Some current complaints and notes are that some files seem to inherit sytest's vague naming scheme (`apidoc`, `federation`, etc.), some simply document and test MSCs, and some restrict themselves to very narrow scopes (`account_change_password_pushers_test.go`)

Inizia esaminando i nomi dei file e i modelli di raggruppamento esistenti nel repository dei test, inclusi esempi come apidoc, federation, test relativi a MSC e account_change_password_pushers_test.go. Il lavoro è completato quando è stato concordato e applicato a tutti i test interessati un approccio coerente alla denominazione e al raggruppamento dei test.

Scritto dal modello di indicizzazione a partire dal testo della issue.