Update Frontend Site to match new Web Presence

[confused-Techie]

The major focus of this PR is to update the frontend site to match with our new web style and presence. Taking cues from how we handle our website everywhere else to get this one updated.

That does mean we are now removing support for the different themes that existed here unfortunately.

Additionally in this PR:

• I've simplified the logic of rendering views to embed everything right into the HTTP handler
• I've also simplified our OpenGraph data generation logic
• Removed the previous way to display timing information about the frontend, and instead we now follow the ServerTiming standard.
• Removed the /status page, instead using the Server header
• Used our sidebar styling for a dedicated section to display service details, as well as now showing dependencies and keywords.
• Finally added the advanced search features as a sidebar to the package listing page

There's still several places I hope to work more on the site, but those are out of the scope of this original PR

[savetheclocktower]

Not quite ready yet!

But maybe I'll take a whack at it when I get a moment.

[confused-Techie]

@savetheclocktower Curious

[savetheclocktower]

Ah:

[savetheclocktower]

OK, got it working. I'll still take a pass on this and see if I can spruce some things up.

[confused-Techie]

@savetheclocktower Great catch on missing the error pages, I'll add those in.
But yeah if you are able to that'd be awesome, since otherwise I'm pretty sure I've gotten everything I want in there

[savetheclocktower]

Random thought: this new site advertises the ability to search for services while specifying the service version (i.e., “give me all autocomplete.provider service providers that use version 4.0.0. On the provider side that's easy, but on the consumer side it's hard, since technically consumers can specify version ranges instead of specific versions. I could advertise my package as consuming autocomplete-provider versions 3-5 and then it wouldn't come up in a search for 4.0.0.

If we can't easily address this (and I doubt we can) then we should probably hide the search-by-service-version functionality for now.

[savetheclocktower]

OK, I opened a PR against this branch in #145.

[confused-Techie]

@savetheclocktower To the point of having the service version search be understanding of semver, that's not yet currently possible. But is a great idea, that I will add as a feature request of the backend, since that would be really handy to have

[confused-Techie]

@savetheclocktower Think we are now good to merge this one?

[savetheclocktower]

Would that automatically upgrade https://packages.pulsar-edit.dev/ to the new look and feel?

I might spend a half-hour or so tonight just doing some stress-testing, but I think this could land very soon.

[confused-Techie]

@savetheclocktower Once merged I'd still need to deploy the new revision to GCP, but I'd very likely do that immediately and unless we wanted to be fancy with AB testing it'd rollout right away

EDIT:

So stress testing prior is not a bad idea at all and give us some time trying to break things, especially on mobile

[savetheclocktower]

@confused-Techie, does the Install button work for you at all on the site? If not, we should hold off until we get it working. It's not doing anything for me.

[confused-Techie]

@savetheclocktower It looks like I forgot the link on the package listing page, but check if the install button works on a single package page, and I'll add the link

[savetheclocktower]

Yeah, it works on single package pages. 👍

[confused-Techie]

Yeah, it works on single package pages. 👍

Fix is in for all pages btw, so we should be good

[confused-Techie]

@savetheclocktower Thanks for the approval! I'll go ahead and merge this one!