docs: fixing a few more places we missed "secure" during rename (#14395)

ui/tests/acceptance/variables-test.js

@@ -25,7 +25,7 @@ import Layout from 'nomad-ui/tests/pages/layout';
 const VARIABLE_TOKEN_ID = '53cur3-v4r14bl35';
 const LIMITED_VARIABLE_TOKEN_ID = 'f3w3r-53cur3-v4r14bl35';
 
-module('Acceptance | secure variables', function (hooks) {
+module('Acceptance | variables', function (hooks) {
   setupApplicationTest(hooks);
   setupMirage(hooks);
   hooks.beforeEach(async function () {

website/content/api-docs/quotas.mdx

@@ -74,7 +74,7 @@ $ curl \
             }
           ]
         },
-        "SecureVariablesLimit": 1000
+        "VariablesLimit": 1000
       }
     ],
     "ModifyIndex": 56,
@@ -138,7 +138,7 @@ $ curl \
           }
         ]
       },
-      "SecureVariablesLimit": 1000
+      "VariablesLimit": 1000
     }
   ],
   "ModifyIndex": 56,

website/content/docs/concepts/security.mdx

@@ -259,9 +259,9 @@ The following are not part of the threat model for server agents:
   system through various means) results in almost all aspects of the agent
   being compromised including access to certificates and other secrets.
 
-- **Existence of [Secure Variables] metadata** - Access to Secure
-  Variables List APIs is controlled by ACL policies, but the existence
-  of specific paths or metadata is not considered sensitive.
+- **Existence of [Variables] metadata** - Access to Variables List APIs is
+  controlled by ACL policies, but the existence of specific paths or metadata is
+  not considered sensitive.
 
 The following are not part of the threat model for client agents:
 
@@ -331,4 +331,4 @@ There are two main components to consider to for external threats in a Nomad clu
 | **4648** / TCP + UDP | Servers | [gossip](/docs/concepts/gossip) protocol to manage server membership using [Serf](https://www.serf.io/).                                                                           |
 
 
-[Secure Variables]: /docs/concepts/secure-variables
+[Variables]: /docs/concepts/variables