Updated documentation for Node24 support in agent (#5437)

Co-authored-by: Sanju Yadav <sanjuyadav@microsoft.com>

Author: sanjuyadav24

docs/node6.md

@@ -8,7 +8,7 @@ As Node versions exit out of the upstream maintenance window, some Pipelines tas
 
 To accommodate this, we have 2 flavors of packages:
 
-| Packages             | Node versions | Description                |
-|----------------------|---------------|----------------------------|
-| `vsts-agent-*`       | 6, 10, 16, 20 | Includes all Node versions that can be used as task execution handler |
-| `pipelines-agents-*` | 16, 20        | Includes only recent Node versions. The goal for these packages is to not include any end-of-life version of Node. |
+| Packages             | Node versions    | Description                |
+|----------------------|------------------|----------------------------|
+| `vsts-agent-*`       | 6, 10, 16, 20, 24 | Includes all Node versions that can be used as task execution handler |
+| `pipelines-agents-*` | 16, 20, 24       | Includes only recent Node versions. The goal for these packages is to not include any end-of-life version of Node. |

docs/noderunner.md

@@ -1,6 +1,6 @@
 # Node 6 support
 
-Agent tasks can be implemented in PowerShell or Node. The agent currently ships with three versions of Node that tasks can target: 6, 10 & 16.
+Agent tasks can be implemented in PowerShell or Node. The agent currently ships with multiple versions of Node that tasks can target: 6, 10, 16, 20 & 24.
 
 Since Node 6 has long passed out of the upstream maintenance window, and all officially supported tasks are migrated from Node 6 to Node 10, Node 6 soon will be removed from the agent package. 
 It's also highly recommended to third-party task maintainers migrate tasks to Node 10 or Node 16.