Add support to detect new Stars "browser" and Star Lists pages

[lstn]

Github added some new functionality with Star Lists recently: https://docs.github.com/en/get-started/exploring-projects-on-github/saving-repositories-with-stars#organizing-starred-repositories-with-lists

And it seems they shadow added a new Stars browser (cannot find documentation for that) that is available at /stars.

I've added the following functions to detect these paths as I can foresee a few features that could be cool to include in Refined Github to enhance them, especially the Star Lists:

isStars URL implementation table

Toggle isStars table

URL	Return Value	Notes
https://github.com/stars	true	Always true. 🔒 login is required on this page - Will always be the user's own profile
https://github.com/stars/lstn	true	🔑 open - no login required - Will be any users Stars "browser" as specified by the second part of the pathname, although if not logged in the sidebar that lets you filter starred repos and topics by author and languages does not appear
https://github.com/stars/lstn/repositories	true	🔑 open - no login required - Will be any users Stars "browser" showing only repositories (not topics) as specified by the second part of the pathname, although if not logged in the sidebar that lets you filter starred repos by author and languages does not appear
https://github.com/stars/lstn/topics	true	🔑open - no login required - Will be any users Stars "browser" showing only topics (not repos) as specified by the second part of the pathname, although if not logged in the sidebar that lets you jump back to repos does not show up
https://github.com/stars/lstn/lists	false	Always false. ⚠️ For some reason, this is a 404 even though further subpaths are implemented. What you expect to show up here actually appears on the regular /username?tab=stars page instead.
https://github.com/stars/lstn/lists/test	true	🔑 open - no login required - Will be any users Star List as specified by the last element of the path, however 🟠_it shows on the /username profile UI, not the "Stars Browser" UI._

isOwnStars URL implementation table

Note: I noticed the current isOwn... methods do not have URL tests associated with them currently, so I did not add any for these in the code.

Toggle isOwnStars table

URL	Return Value	Notes
https://github.com/stars	true	Always false. See isStars table
https://github.com/stars/lstn	true or false	See isStars table. Return value determined by isLoggedIn
https://github.com/stars/lstn/repositories	true or false	See isStars table. Return value determined by isLoggedIn
https://github.com/stars/lstn/topics	true or false	See isStars table. Return value determined by isLoggedIn
https://github.com/stars/lstn/lists	false	Always false. ⚠️ For some reason, this is a 404 even though further subpaths are implemented. These show up on the regular /username?tab=stars page instead.
https://github.com/stars/lstn/lists/test	true or false	See isStars table. Return value determined by isLoggedIn

isStarsList URL implementation table

Toggle isStarsList table

URL	Return Value	Notes
All other URLs mentioned in above tables	false
https://github.com/stars/lstn/lists/test	true	🔑 open - no login required - Will be any users Star List as specified by the last element of the path, however it shows on the /username profile UI, not the "Stars Browser" UI.

isOwnStarsList URL implementation table

Note: I noticed the current isOwn... methods do not have URL tests associated with them currently, so I did not add any for these in the code.

Toggle isOwnStarsList table

URL	Return Value	Notes
All other URLs mentioned in above tables	false
https://github.com/stars/lstn/lists/test	true or false	See isStarsList table. Return value determined by isLoggedIn

On a couple things I did/didn't include:

• I was conflicted on including the isOwn... implementations. In my head, they seemed like they could be useful for some Refined Github features that would apply only the the user's Star Lists, so I added them. If you don't feel like they fit here, I'm not opposed to removing them but I genuinely can think of a couple examples where they might be useful down the line and they'd end up getting added anyway in the future.
• I didn't include isStarsRepositories or isStarsTopics or the isOwn... version of them as they are essentially and functionally the exact same UX as the other "Star Browser" pages (except the Stars List page itself)
• I didn't include the /username?tab=stars URL to isStars or isOwnStars for basically the same reason - the UX is drastically different on these pages, which I can't imagine would be useful at all for anyone using these checks to implement features on Refined Github. In fact, I can see it being a hindrance that makes these checks unusable for now until Github decides to further change this UX and go all in on the "Stars Browser" or whatever they are calling it.

[lstn]

I'll admit I'm not usually a frontend dev and TS/JS is very rare for me to write so I can't quite figure out how to the the CI Test job to not fail for those IsOwn... functions not having test URLs. Might need a pointer here 🤷

[fregante]

I can foresee a few features that could be cool to include in Refined Github to enhance them

We only add detections to this package if there's an immediate need for them. If not, we don't

[lstn]

I can foresee a few features that could be cool to include in Refined Github to enhance them

We only add detections to this package if there's an immediate need for them. If not, we don't

Right - so if I wanted to implement a feature that relies on the new StarsList page in Refined Github, I'd have to submit this PR at the same time instead of doing it before?

[fregante]

Ideally you'd ask about the issue first so that when you open this PR here, you can point back to it. Given the state of GitHub at the moment it's very unlikely we add new features, especially for secondary pages like star lists.