Fix external link icons in the documentation

docs/modules/superset/pages/usage-guide/security.adoc

@@ -40,7 +40,7 @@ spec:
 <1> The reference to an AuthenticationClass called `ldap`
 <2> The default role to which all users are assigned
 
-Users that log in with LDAP are assigned to a default https://superset.apache.org/docs/security/#roles[Role] which is specified with the `userRegistrationRole` property.
+Users that log in with LDAP are assigned to a default https://superset.apache.org/docs/security/#roles[Role^{external-link-icon}^] which is specified with the `userRegistrationRole` property.
 
 You can follow the xref:home:tutorials:authentication_with_openldap.adoc[] tutorial to learn how to set up an AuthenticationClass for an LDAP server, as well as consulting the xref:home:concepts:authentication.adoc#_ldap[AuthenticationClass concepts page].
 
@@ -49,7 +49,8 @@ You can follow the xref:home:tutorials:authentication_with_openldap.adoc[] tutor
 An OpenID Connect provider can be used for authentication.
 Unfortunately, there is no generic support for OpenID Connect built into Superset.
 This means that only specific OpenID Connect providers can be configured.
-IMPORTANT: Superset deployments on the Stackable Data Platform only support https://www.keycloak.org/[Keycloak {external-link-icon}^].
+
+IMPORTANT: Superset deployments on the Stackable Data Platform only support https://www.keycloak.org/[Keycloak^{external-link-icon}^].
 
 [source,yaml]
 ----
@@ -72,7 +73,7 @@ spec:
 <2> The reference to the Secret containing the Superset client credentials
 <3> The default role to which all users are assigned
 
-Users that log in with OpenID Connect are assigned to a default https://superset.apache.org/docs/security/#roles[Role] which is specified with the `userRegistrationRole` property.
+Users that log in with OpenID Connect are assigned to a default https://superset.apache.org/docs/security/#roles[Role^{external-link-icon}^] which is specified with the `userRegistrationRole` property.
 
 The Secret containing the Superset client credentials:
 
@@ -119,15 +120,15 @@ Further information for specifying an AuthenticationClass for an OIDC provider c
 == [[authorization]]Authorization
 
 Superset has a concept called `Roles` which allows you to grant user permissions based on roles.
-Have a look at the https://superset.apache.org/docs/security[Superset documentation on Security].
+Have a look at the https://superset.apache.org/docs/security[Superset documentation on Security^{external-link-icon}^].
 
 === Superset database
 
 You can view all the available roles in the web interface of Superset and can also assign users to these roles.
 
 === LDAP
 
-Superset supports assigning https://superset.apache.org/docs/security/#roles[Roles] to users based on their LDAP group membership, though this is not yet supported by the Stackable operator.
+Superset supports assigning https://superset.apache.org/docs/security/#roles[Roles^{external-link-icon}^] to users based on their LDAP group membership, though this is not yet supported by the Stackable operator.
 All the users logging in via LDAP get assigned to the same role which you can configure via the attribute `authentication[*].userRegistrationRole` on the `SupersetCluster` object:
 
 [source,yaml]
@@ -148,7 +149,7 @@ spec:
 === OpenID Connect
 
 The mechanism for assigning roles to users described in the LDAP section also applies to OpenID Connect.
-Superset supports assigning https://superset.apache.org/docs/security/#roles[Roles] to users based on their OpenID Connect scopes, though this is not yet supported by the Stackable operator.
+Superset supports assigning https://superset.apache.org/docs/security/#roles[Roles^{external-link-icon}^] to users based on their OpenID Connect scopes, though this is not yet supported by the Stackable operator.
 All the users logging in via OpenID Connect get assigned to the same role which you can configure via the attribute `authentication[*].userRegistrationRole` on the `SupersetCluster` object:
 
 [source,yaml]