fix: use full url for linking to api doc

[jjtang1985]

Context

I made a mistake to commit to the document branch directly, which tried to use the useBaseUrl .
Switched to the full url.

Here is an related issue, saying there can be false positive and how to disable it via config.
However, the config is about to change navbar/footer items, which is not applicable in our case.

Definition of Done

Please consider all items and remove only if not applicable.

• Tests created/adjusted for your changes.
• Release notes updated.
  • Provide sufficient context so that each entry can be understood on its own.
  • Be specific about names of functions, classes, modules, etc.
  • Describe when or where this is relevant
  • Use indicative and present tense. For example, write "Provide function name that does X in order to Y" over "Now X can be done by calling a new function".
• PR title adheres to conventional commit guidelines (please note that only fix: and feat: will end up in the release notes)
• If applicable: Properly documented (JSDoc of public API)
• If applicable: Check if node run doc still works.

[FrankEssenberger]

Fine for me, but what will happen locally? The link will point to the internet and not the local static copy of the API right?