token-scopes: Remove endpoint scope preselection paragraph

We might want to discuss the default endpoint scope separately. It could be beneficial to not select anything by default, or just `publish-update` as a default for CI systems.

Author: Turbo87

text/0000-crates-io-token-scopes.md

@@ -48,11 +48,6 @@ adding the following endpoint scopes:
 More endpoint scopes might be added in the future without the need of a
 dedicated RFC.
 
-The crates.io UI will pre-select the scopes needed by the `cargo` CLI, which at
-the time of writing this RFC are `publish-new`, `publish-update`, `yank` and
-`change-owners`. The user will have to explicitly opt into extra scopes or the
-legacy permission model.
-
 Tokens created before the implementation of this RFC will default to the legacy
 scope.