doc: remove deprecated nearup references (#138)

* doc(node-docs): remove deprecated nearup references

* doc(node-docs): restore non-nearup content for macos/linux and windows guides

* doc: fix intro text to say RPC node instead of validator node

* doc: fix sidebar_position collisions for macos/linux and windows guides

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: darioush

docs/archival/run-archival-node-with-nearup.md

@@ -1,24 +1,24 @@
 ---
-id: run-archival-node-without-nearup
+id: run-archival-node
 title: Run an Archival Node
 sidebar_label: Run a Node 🚀
 sidebar_position: 2
-description: How to run an Archival Node without nearup
+description: How to run an Archival Node
 ---
 ## This page is DEPRECATED in favor of split storage archival.  Please Use [Run a Split Storage Archival](/archival/split-storage-archival)
 
 The following instructions are applicable across localnet, testnet, and mainnet.
 
 If you are looking to learn how to compile and run a NEAR Archival node natively for one of the following networks, this guide is for you.
 
-- [`testnet`](/archival/run-archival-node-without-nearup#testnet)
-- [`mainnet`](/archival/run-archival-node-without-nearup#mainnet)
+- [`testnet`](/archival/run-archival-node#testnet)
+- [`mainnet`](/archival/run-archival-node#mainnet)
 
 
 <blockquote class="info">
 <strong>Heads up</strong><br /><br />
 
-Running an archival node is very similar to running a [validator node](/validator/running-a-node) as both types of node use the same `nearcore` release. The main difference for running an archival node is a modification to the `config.json` by changing `archive` to `true`. See below for more details.
+Running an archival node is very similar to running a [validator node](/validator/compile-and-run-a-node) as both types of node use the same `nearcore` release. The main difference for running an archival node is a modification to the `config.json` by changing `archive` to `true`. See below for more details.
 
 </blockquote>
 

…ival/run-archival-node-without-nearup.md docs/archival/run-archival-node.mddocs/archival/run-archival-node-without-nearup.md renamed to docs/archival/run-archival-node.md docs/archival/run-archival-node-without-nearup.md renamed to docs/archival/run-archival-node.md

@@ -1,23 +1,23 @@
 ---
-id: run-rpc-node-without-nearup
+id: run-rpc-node
 title: Run an RPC Node
 sidebar_label: Run a Node 🚀
 sidebar_position: 2
-description: How to run an RPC Node without nearup
+description: How to run an RPC Node
 ---
 
 The following instructions are applicable across localnet, testnet, and mainnet.
 
 If you are looking to learn how to compile and run a NEAR RPC node natively for one of the following networks, this guide is for you.
 
-- [`testnet`](/rpc/run-rpc-node-without-nearup#testnet)
-- [`mainnet`](/rpc/run-rpc-node-without-nearup#mainnet)
+- [`testnet`](/rpc/run-rpc-node#testnet)
+- [`mainnet`](/rpc/run-rpc-node#mainnet)
 
 
 <blockquote class="info">
 <strong>Heads up</strong><br /><br />
 
-Running a RPC node is very similar to running a [validator node](/validator/running-a-node) as both types of node use the same `nearcore` release. The main difference for running a validator node is requiring `validator_key.json` to be used by the validator node to support its work of validating blocks and chunks on the network.
+Running a RPC node is very similar to running a [validator node](/validator/compile-and-run-a-node) as both types of node use the same `nearcore` release. The main difference for running a validator node is requiring `validator_key.json` to be used by the validator node to support its work of validating blocks and chunks on the network.
 
 </blockquote>