feat(appkit): introduce Lakebase plugin

[pkosiec]

This PR introduces a thin wrapper on top of the Lakebase driver, to ensure consistent behavior.

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

Notes

Should we really name it as "Lakebase"? Victor suggested using name "Transaction" but it doesn't resonate with me.

On the other hand, oltp, database, postgres don't sound like better options than lakebase 🤔 We need to distinguish this plugin with the analytics plugin somehow.

IMO the "Lakebase" name is the best what we can do right now, even though it is not consistent with analytics plugin. Let's see how the other plugins are named and then rename it - or, if you have any ideas, feel free to suggest them already.

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

[MarioCadenas]

In general code LGTM, I'm not so sure about the onSetupMessage thing though, let's discuss that

[MarioCadenas]

so if we have multiple plugins, with the onSetupMessage, then we will have multiple instructions printing? also, this seems like something needed just for the lakebase plugin and not for a general use case, what other use cases do you see?

[pkosiec]

so if we have multiple plugins, with the onSetupMessage, then we will have multiple instructions printing?

yes, per plugin 👍

For now it is used for Lakebase, but I can imagine other plugins that require some manual steps - something what CLI / AppKit cannot do automatically - for example, an external service setup "Create a Slack webhook and set env SLACK_WEBHOOK_URL"

I can see value especially in the external / third party plugins. I totally agree that with our plugins we should aim to not print such messages and have everything provided out of the box.

This is completely optional for plugins, and it doesn't change the goal of having the plugins zero-config 👍