Move Bot creation utilies to @medplum/core

[rahul1]

User Driven: https://medplum.slack.com/archives/C05C5KXTPJA/p1694180812426259

Use Case

In a B2B2B use case, our medplum user is spinning up a new project for each of their customers. As part the project setup process, they would like to populate the project with a set of standard Bots.

To do this, their backend service will call the Medplum API with both the source and compiled contents of the Bot.

Proposal

Move the following functions from the CLI bot utils code into @medplum/core:

• createBot
• saveBot
• deployBot

with appropriate changes to the argument. This would allow any TS backend service to programatically create Bots.

[codyebberson]

We should discuss this.

The utility methods referenced have dependencies on Node.js file system operations (readFileSync, etc), which gets messy in the context of @medplum/core.

I also have mixed feelings about finding the right threshold of abstraction for what we include in @medplum/core. @medplum/core is already big, and we should be judicious about when we choose to include things.

To be clear, everything in those methods is possible today. The discussion here is about what level of convenience should be included in @medplum/core.