Publishing room to homeserver room directory should not require m.room.canonical_alias permission


### Description

On current riot.im/app (1.6.2), not having the `m.room.canonical_alias` room permission disables all controls in _Room settings -> Room Addresses_, including the _Publish this room to the public in tcharles.fr's room directory?_ switch.
I don't think this is expected behaviour as the permission for this feature is set in Synapse config (`room_list_publication_rules`), and querying directly the endpoint using curl (PUT on `_matrix/client/r0/directory/list/room/:roomID`) is still allowed without having the m.room.canonical_alias permission.

### Steps to reproduce

- Using a default synapse instance (or matrix.org)
- Create an empty room
- Demote yourself to Default or invite a new user
- Open _Room settings -> Room Addresses_, the publish button is disabled and can't be toggled.

Logs being sent: no

### Version information

- **Platform**: web
- **Browser**: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
- **OS**: Windows
- **URL**: riot.im/app

Start in the web client's Room settings → Room Addresses controls and trace the permission check against m.room.canonical_alias; compare it with the PUT _matrix/client/r0/directory/list/room/:roomID behavior described here. Done means publishing can be toggled when the configured room-directory rule allows it, without requiring the canonical-alias permission, and the reproduction steps no longer show disabled controls.

Written by the indexing model from the issue text.