Added spinner on retrieving bind key in the client

[tuj]

Link to issue

#380

Link to ticket

https://leantime.itkdev.dk/#/tickets/showTicket/7203

Description

Builds on #387

Added spinner on retrieving bind key in the client.

Checklist

• My code is covered by test cases.
• My code passes our test (all our tests).
• My code passes our static analysis suite.
• My code passes our continuous integration process.

[turegjorup]

Refactor and the UNKNOWN/default fix look good — that case previously froze the polling loop, which is a real fix worth highlighting.

Bug

• Spinner shows on top of admin previews. retrievingBindKey is initialized to true and only cleared in startContent and the READY/AWAITING_BIND_KEY branches. For non-screen preview modes (slide, playlist, theme, …), useEffect skips startContent and never touches the flag, so retrievingBindKey && !bindKey stays true and the spinner sits in the bottom-right corner of every admin preview. Suggest gating on !preview or initializing from preview === null. (app.jsx:299-303)

Nits

• .catch in checkLogin doesn't clear retrievingBindKey, so a degraded API leaves the spinner running forever with no error surfaced. Probably intentional, but worth a comment. (app.jsx:148-150)
• Test file app-reauth.test.jsx contains two describes, only one of which is about reauth — the other is about UNKNOWN-status polling. Rename or split.
• Neither test actually asserts on the spinner element (the headline feature). One expect(document.querySelector(".retrieving-bind-key-spinner")).toBeInTheDocument() before/after would close that gap.
• @keyframes spin is declared globally in app.scss. No collision today, but a more specific name (e.g. bind-key-spin) avoids future ones.

[turegjorup]

Posting the earlier findings as inline suggestions for easier action. See top-level review for rationale; comments below carry the concrete diffs.

[turegjorup]

Nit: the .catch handler below doesn't clear retrievingBindKey, so a degraded API leaves the spinner running indefinitely with no error surfaced. Probably intentional (we're still trying), but worth a one-line comment explaining the choice — or surfacing statusService.setError(...) on repeated failures.

[turegjorup]

Nit: this describe is about polling on LOGIN_STATUS_UNKNOWN, not reauth — the file name app-reauth.test.jsx is misleading. Either rename the file (e.g. app-bind-key.test.jsx) or split the unknown-status case into its own file.

[turegjorup]

Nit: the headline feature of this PR is the spinner, but neither test asserts on the spinner element. Easy gap to close:

Suggested change

	expect(screen.queryByText("BIND42")).not.toBeInTheDocument();
	expect(screen.queryByText("BIND42")).not.toBeInTheDocument();
	expect(document.querySelector(".retrieving-bind-key-spinner")).toBeInTheDocument();

And a complementary not.toBeInTheDocument() after the bind key arrives at line 140.