feat: replace the /hardware with new denormalized view and remove /hardware-new

[gustavobtflores]

Description

Promote the new, optimized hardware listing page to be the default view (/hardware) and move the legacy view to an archive route.

[MarceloRobert]

Is there really a need to do both cases for the same value? IMO you can have just one case for that value and use it in both pages

[gustavobtflores]

didn't get it tbh, why we wouldn't need both cases here?

[MarceloRobert]

because whenever you would use /hardware/v1 you can just use /hardware since they are exactly the same and don't need semantic differentiation

[AmadeusK525]

I guess if you renamed the old one to v1 you should rename the new one to v2, no?

[gustavobtflores]

I guess if you renamed the old one to v1 you should rename the new one to v2, no?

My concern with /hardware/v2 is that it would require redirecting users from /hardware, which adds avoidable complexity. I'd prefer to keep the new one at /hardware and the old one at /hardware/v1

[MarceloRobert]

I guess if you renamed the old one to v1 you should rename the new one to v2, no?
@AmadeusK525

It's best if we keep the route as /hardware for backwards compatibility and also because we don't need to increase the url size for no reason. What could be done is what I did for the treeListing on #1709 which is to have three routes: /tree/v1, /tree/v2, and just /tree, meaning routes for specific version and a route for the latest/main version

[MarceloRobert]

@gustavobtflores there seems to not have much change since the last time I reviewed the PR, you can let me resolve my comments once I see that they have been solved

[MarceloRobert]

I noticed that in the /hardware/v1 route when I change the origin it goes back to the /hardware route. I did change the OriginSelector on my PR, so maybe it's worth checking those changes here

[MarceloRobert]

Seems great