DOCSP-26449 Replace access control-aggregations docs (#2299)

* DOCSP-26449 replace with refs

* one last replacement

Author: lindseymoore

source/core/authorization.txt

@@ -53,7 +53,7 @@ cluster, the affiliated actions affect the state of the system rather
 than a specific database or collection. For information on the resource
 documents, see :doc:`/reference/resource-document`.
 
-An :doc:`action </reference/privilege-actions>` specifies the operation
+An :ref:`action <security-user-actions>` specifies the operation
 allowed on the resource. For available actions see
 :doc:`/reference/privilege-actions`.
 

source/core/collection-level-access-control.txt

@@ -24,7 +24,7 @@ that grant privileges on a collection level.
 Privileges and Scope
 --------------------
 
-A privilege consists of :doc:`actions </reference/privilege-actions>`
+A privilege consists of :ref:`actions <security-user-actions>`
 and the :doc:`resources </reference/resource-document>` upon which the
 actions are permissible; i.e. the resources define the scope of the
 actions for that privilege. 

source/core/transactions-production-consideration.txt

@@ -136,7 +136,7 @@ pressure.
 Transactions and Security
 -------------------------
 
-- If running with :doc:`access control </core/authorization>`, you must
+- If running with :ref:`access control <authorization>`, you must
   have :doc:`privileges </reference/built-in-roles>` for the
   :ref:`operations in the transaction <transactions-operations>`.
 

source/includes/access-mongodump-collections.rst

@@ -1,5 +1,5 @@
 To run :binary:`~bin.mongodump` against a MongoDB deployment that has
-:doc:`access control </core/authorization>` enabled, you must have
+:ref:`access control <authorization>` enabled, you must have
 privileges that grant :authaction:`find` action for each database to
 back up. The built-in :authrole:`backup` role provides the required
 privileges to perform backup of any and all databases.

source/includes/introduction-deploy-replica-set.rst

@@ -1,6 +1,6 @@
 This tutorial describes how to create a three-member :term:`replica
 set` from three existing :binary:`~bin.mongod` instances running with
-:doc:`access control </core/authorization>` disabled.
+:ref:`access control <authorization>` disabled.
 
 To deploy a replica set with enabled :doc:`access control
 </core/authorization>`, see

source/reference/glossary.txt

@@ -40,7 +40,7 @@ Glossary
    action
       An operation the user can perform on a resource. Actions and
       :term:`resources <resource>` combine to create :term:`privileges
-      <privilege>`. See :doc:`action </reference/privilege-actions>`.
+      <privilege>`. See :ref:`action <security-user-actions>`.
 
    admin database
       A privileged database. Users

source/reference/method/Session.startTransaction.txt

@@ -84,7 +84,7 @@ Operations Supported within a Transaction
 
 .. note::
 
-   If running with :doc:`access control </core/authorization>`, you
+   If running with :ref:`access control <authorization>`, you
    must have privileges for the :ref:`operations in the transaction
    <transactions-operations>`.