Config storage doesn't require space permissions anymore

Related dev. issue(s): GitHub link(s)

Product: Tarantool (+ TDB and TCF docs)
Since: future versions - 3.5.0, 3.4.1, 3.3.3, 3.2.2
Root documents:

• https://www.tarantool.io/en/doc/latest/platform/configuration/configuration_etcd/
• https://www.tarantool.io/en/doc/latest/platform/configuration/configuration_etcd/#setting-up-a-configuration-storage

SME: @ Totktonada

Details

Previously permissions to read/write internal config storage spaces were
required:

- permissions: [read, write]
  spaces:
    - config_storage
    - config_storage_meta

Now, the config.storage.* API functions have access to these spaces
without an explicit permissions configuration. These permissions can be
removed from the configuration.

This change is planned for inclusion into 3.5.0, 3.4.1, 3.3.3, 3.2.2
releases.
Requested by @Totktonada in https://github.com/tarantool/tarantool-ee/commit/b655f0054d4158cd4b81ae74a9ce5c934c12fbb6.

TDB and TCF tickets: #5194 #5195

Open the configuration_etcd documentation and the “Setting up a configuration storage” section named in the issue. Review the YAML permissions example and the surrounding version notes, then update the documentation to reflect that config.storage.* access no longer requires explicit permissions for config_storage and config_storage_meta. Check the related TDB and TCF tickets for any corresponding documentation scope.