Preview at surge.sh is broken

We have a preview step in our pipelines that seems to deploy a website-preview on surge.sh. However, the deployment fails due to invalid token (see error log).

We should either, fix surge.sh token, drop the preview job or find an alternative.

Run afc163/surge-preview@v1
Found PR number: 334, PR status: opened
RUN: echo "Has build already"
/usr/bin/echo Has build already
Has build already
Build time: 0.011 seconds
Deploy to robotframework-robotframework-github-com-preview-pr-334.surge.sh
/usr/local/bin/npx surge ./docs robotframework-robotframework-github-com-preview-pr-334.surge.sh --token ***
npm warn exec The following package was not found and will be installed: surge@0.24.6
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated glob@7.2.3: Glob versions prior to v[9](https://github.com/robotframework/robotframework.github.com/actions/runs/13761157742/job/38477393710#step:4:10) are no longer supported
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated fstream@1.0.[12](https://github.com/robotframework/robotframework.github.com/actions/runs/13761157742/job/38477393710#step:4:13): This package is no longer supported.
npm warn deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3[14](https://github.com/robotframework/robotframework.github.com/actions/runs/13761157742/job/38477393710#step:4:15)2

   Invalid token

error message:
{}

Inspecione a etapa de visualização do pipeline que invoca afc163/surge-preview@v1 e analise o log da implantação com falha que mostra um token inválido; nenhum nome de arquivo de workflow é fornecido. Determine se o job de visualização pode ser restaurado ou se deve ser removido ou substituído e, em seguida, verifique se o pipeline não falha mais e se o comportamento pretendido da visualização está claro.