chore: generate template dynamically for specific enabled plugins

[pkosiec]

First phase of the dynamic template, that works with analytics and/or lakebase plugins.

Resolves https://databricks.atlassian.net/browse/LKB-9681

Video

lakebase-template.mp4

All PRs

1. CLI: Display plugin setup instructions after apps init flow, remove empty files after template rendering cli#4549
2. feat(lakebase): add ability to lookup DB username with API #123
3. feat(appkit): introduce Lakebase plugin #126
4. chore: generate template dynamically for specific enabled plugins #127

Scope

We agreed on the following scope:

1. remove harcoded paths on CLI - maybe just trigger an npm command as a part of the template at the end (if necessary, let's see)
2. from the template, I'll use Go templates to conditionally add/remove files content

[MarioCadenas]

since the server is already defined as "requiredByTemplate" it will be added automatically, we don't have to hard code it, what would be nice is to get the config from the manifest and inject it here instead, but I guess that can be added later. But this seems very specific to lakebase so it can extend the routes, maybe we can do this in a different way?

[MarioCadenas]

this is all very coupled to each plugin, right now the cli populates the env vars based on the resources from the manifest so we wouldn't need this for analytics.

I wonder if we can make it in a different way for lakebase so we can keep what we had instead of putting ifs all around checking for each plugin

[MarioCadenas]

I think some of these are being used by some of the components we have, why are we deleting them?

[MarioCadenas]

I wouldn't do this 😅

[MarioCadenas]

I like the idea of making the template even more dynamic, but there are some things we need to polish 😄.
We also need to be very careful when we merge this. The template pinning should be merged before this, your changes on the CLI to use this template, and the CLI released with it, if not we can't merge this as it has a lot of breaking changes on the template