build: last test of the stale feature action

- set the days so that we process ~ 40 issues
  so that we can see what kind of feedback we get
  on saying we are going to close stale feature requests
- set the label to stale instead of stalled so that
  there is no race with the action that closes stalled
  issues
- fix the links to the feature management doc

Signed-off-by: Michael Dawson <mdawson@devrus.com>

PR-URL: #42085
Reviewed-By: Mestery <mestery@protonmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>

.github/workflows/close-stale-feature-requests.yml

@@ -15,7 +15,7 @@ env:
 
     For more information on how the project manages
     feature requests, please consult the
-    [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/guides/feature-request-management.md).
+    [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).
 
   WARN_MESSAGE: >
     There has been no activity on this feature request for
@@ -25,7 +25,7 @@ env:
 
     For more information on how the project manages
     feature requests, please consult the
-    [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/guides/feature-request-management.md).
+    [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md).
 # yamllint enable
 
 jobs:
@@ -36,9 +36,9 @@ jobs:
       - uses: actions/stale@v4
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
-          days-before-stale: 1226
+          days-before-stale: 906
           days-before-close: 30
-          stale-issue-label: stalled
+          stale-issue-label: stale
           close-issue-message: ${{ env.CLOSE_MESSAGE }}
           stale-issue-message: ${{ env.WARN_MESSAGE }}
           only-labels: feature request