Add page: offer the game's fixes right after a Fetch

[cheapmanga]

After a Fetch on the Add page, when the game has published fixes, a banner names them and takes you there:

This game has 1 fix(es) available: Online Fix. [ See fixes ]

The button opens the Fixes page with that game already unfolded — the same route luatools://fix/ takes.

Why it names the kind. The endpoint is /api/denuvo/listings, but of the 1759 games it returns, 1621 are tagged "Online Fix" and no tag named "Denuvo" exists at all. Calling them Denuvo fixes would be wrong nearly every time, so the banner uses the tags the Fixes page already shows as pills. No tags on a game's fixes → plain sentence, no kinds.

Three behaviours worth knowing:

• The lookup runs alongside the source check, never before it: whether a fix exists has no bearing on fetching manifests, so a Fetch is never held up by it.
• A result that lands after the user moved on is dropped, so the banner can't advertise the previous game's fixes.
• Games only — a DLC's fetch is about its depots, and a fix belongs to the base game. API unreachable means no banner, never an error.

FixLookupService fetches the listing once per session and keeps an appid → summary map, so the check is free after the first lookup.

Both strings are translated in all 29 languages; scripts/check-i18n.py passes. Rebased on main at 1.3.0: dotnet build -c Release is 0 warnings, 0 errors.

_{This PR previously also carried an Achievements page. That part is dropped — #37 was there first — so what is left is only the Add-page banner. The branch keeps its old name; its contents are just this.}

[not1cyyy]

@cheapmanga did you deadass take my contribution and open a pull request under your name ? what a shame lol

[Kirkland-Pickles]

you should debundle the feature that you took from noticyyy and only add the "add fixes to fetch" as its own pr.

also a slightly more ideal version of this fixes button would adding the actual fix button to the games page inside the manage tab (given that the manifest needs to apply before the install, and the fix after)

[cheapmanga]

@not1cyyy Your PR came first and that is what matters here, so I have dropped the achievements part from this one — it now only contains the Add-page fix banner, rebased on 1.3.0. Sorry again for the collision; I should have gone through the open PRs before opening mine, and I didn't.

For the record, since I would rather say it plainly than leave it hanging: I wrote mine from gibbed's SAM sources, not from yours, and the two ended up looking alike because SAM's interop is what you vendor and the 32-bit DLL forces a separate worker on everybody. But you were first, your PR stands, and I am not going to argue over who reinvented which wheel.

@Kirkland-Pickles Thanks — that is exactly what I did. And your other point is a better idea than what I built: the fix button belongs on the game's page in the Manage tab, since the manifest goes on before the install and the fix after. Happy to move it there if the maintainer wants it that way; say the word and I will.

[cheapmanga]

To be clear, since my fork's build might suggest otherwise: I removed the achievements tab from this PR, not from my fork — I still use it locally, and anyone downloading my build will see it there. What I'm proposing here is only the Add-page banner.