Fix #1104: Improve lakeinfo structure and reporting

[calina-c]

Closes #1104. Cherry picked from #1129.

TODO: In the meantime, we added tests for our dashboards. I think we should add Dash testing to this dashboard as well, but I would prefer doing it in a different PR.

[calina-c]

Decided with Trent to add some basic unit tests to LakeInfo, in a separate PR.

[idiom-bytes]

@trentmc @calina-c
I'm not sure why all of this was separated from the lake module?

[Problem - Core tooling is being moved to serve FE/webapps]
the core problem is that these tools exist to serve the lake module and help operate the lake along with drop, update, and many other functionalities...

the validations/info/debuggin/operational commands should remain inside of lake module... not moved into something that is to serve FE

[Recommendation - Separate core engine systems and code from webapp functionality]
I believe all frontend/webapp tools should exist in a separate module
/pdr_backend/ -> serves all the core engine systems, apis, etc..
/pdr_frontend/ -> provides all implementations for all webapp requirements

all core functionality for the web apps should then be referenced from pdr_backend

pytest should first run all coverage inside pdr_backend/ and then pdr_frontend/

[we now have 3 clis that are poorly named an structured]
cli/cli_module.py (main cli)
cli/cli_module_lake.py (lake cli)
lake_info/cli.py (lakeinfo cli)

the recommendations above would set a clear API/interface for how core engine functionality is separated from FE/webapp logic

[idiom-bytes]

I have created a ticket requesting that we address this, including separating the webapp logic from engine logic, so we don't run into these problems in the future

#1419

[trentmc]

The "pdr_backend/" directory is meant to house all the code, frontend and backend and everything in between. It's meant to mirror the name of the repo itself. The way that most well structured python repos work. And, needed for pypi. For historical reasons it has "backend" in the name. Let's not change that name right now, it would be a huge pain.

All cli stuff should be in pdr_backend/cli/. It can be cli to run lake, sim, sim plots, predictoor bots, trader bots, or dashboard.

And we have many support directories. Building blocks, if you will. Ppss, util, lake, aimodel, etc etc. They interlink though each has fairly well-defined responsibility.

We should 100% definitely NOT add a new directory parallel to pdr_backend. It would totally mess with the overall structure of the repo, including compromising how it needs to behave for pypi.

And there should definitely not be a directory named frontend/, anywhere. We have sim plots, we have the feed analysis app, and now we have the dashboard app. Each gets their own subdirectory of pdr_backend/, with an appropriate label.