Clean up and document decorators replaced by static maps

[ybnd]

Describe the bug In #2750 some entry component decorators were replaced with static maps, e.g. rendersMenuItemForType and rendersBrowseBy.

There are still a few problems that should be addressed:

• The original decorators still exist, but aren't used. If they aren't meant to be used, they should be removed from the codebase to avoid confusion.
  • Specifically rendersBrowseBy looks broken, as it uses the new static map and the old dynamic map constants interchangeably
• It's unclear how theme support should work for browse-by components now. This should be clarified in the code.
  • Right now, the custom theme versions of these components are not included in the mapping, so they will never be visible in the UI
• The static map pattern replacing rendersBrowseBy is very difficult to read

[ybnd]

A fun way to tackle this problem could be to

• Keep using class decorators for dynamic components
• Generate static maps based on these decorators as a pre-build step

This could be best-of-both worlds in the sense that

• We keep decorators for "DevX"
• We won't have to think about when the decorators are actually invoked, because we'll have a static map
• We could even make entry components lazy without modules/routes or tedious manual import() calls

If this seems like an interesting way to go: I've got a very early proof-of-concept that I could expand on to demonstrate