docs: Change ScrollRef components to Anchor links

[sixhobbits]

removing ScrollRef from frontegg article and everywhere else, see:

FusionAuth/fusionauth-issues#2946

[bradmccarty]

Going to have @mooreds or @mark-robustelli peek at the failing API checks.

Going to have Dan or Mark peek at the check_apis failutres.

[bradmccarty]

@mooreds or @mark-robustelli I think the api checks are outside of my realm of knowledge. Could one of y'all take a peek and handle the approval if they're not of concern?

[mark-robustelli]

@sixhobbits Looks like the api check is failing. Can you please update so the check pass?

opening: /home/runner/work/fusionauth-site/fusionauth-site/fusionauth-client-builder/src/main/domain/io.fusionauth.domain.event.UserUpdateEvent.json
processing userUpdateEvent
retrieving https://fusionauth.io/docs/extend/events-and-webhooks/events/user-update
not traversing event.original, but checking if it is in the content of extend/events-and-webhooks/events/user-update
not traversing event.user, but checking if it is in the content of extend/events-and-webhooks/events/user-update
MISSING FIELDS
{:original_examined_type=>"application.jwtConfiguration.refreshTokenRevocationPolicy", :full_field_name=>"application.jwtConfiguration.refreshTokenRevocationPolicy.onOneTimeTokenReuse", :type=>"boolean"}

[sixhobbits]

@mark-robustelli - we've fixed most of them, then that will leave only this one

Failed Check about br tags
/home/runner/work/fusionauth-site/fusionauth-site/astro/src/content/docs/lifecycle/authenticate-users/oauth/endpoints.mdx
435:145 error Unexpected HTML tag [br], use markdown instead remark-lint-no-html
435:211 error Unexpected HTML tag [br], use markdown instead remark-lint-no-html
435:305 error Unexpected HTML tag [br], use markdown instead remark-lint-no-html
435:394 error Unexpected HTML tag [br], use markdown instead remark-lint-no-html

That's about this table where a bullet list is used inside a table cell.

Because you can't use newlines in a table (it would create new rows), using
s is the only easy way to get this layout

Any suggestions on how to handle this? Should we reword that table, or can we bypass the check for this?

Current table code is

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 302  | The request was successful and the redirect location will be determined by using the configuration values in the following precedence: <br/>* The `post_logout_redirect_uri` request parameter if present<br/>* The <InlineField>logoutURL</InlineField> defined in the Application OAuth configuration<br/>* The <InlineField>logoutURL</InlineField> defined in the Tenant OAuth configuration<br/>* `/` |
| 400  | The request was invalid and/or malformed. The response will contain a JSON message with the specific errors. The error response JSON is covered in the [OAuth Error section](#oautherror) of the API documentation.

[mooreds]

You can bypass checks with

{/* eslint-disable-line */}

Mark is closer to the PR so I'll let him weigh in on what the right path forward is.

[mark-robustelli]

I think we are good with bypassing for this.