[Housekeeping] Add CI tests to flytekit repo: plugins should be importable with flytekit dependencies only

[cosmicBboy]

Describe the issue

The purpose of this issue is to enforce the following convention in flytekitplugins: "I should be able to import flytekitplugins.<plugin> with only flytekit dependencies. This ensures that we use lazy module loading in the plugins (see flyteorg/flytekit#2049).

What if we do not do this?

When new plugins are introduced (or existing ones are extended) contributions can break this convention when new dependencies are added.

Related component(s)

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[dosubot]

🤖

That sounds like a great idea! Enforcing this convention will definitely help maintain consistency and prevent unexpected issues with new plugin contributions. Your proposed solution will be a valuable addition to the flytekit repo. Thank you for considering this improvement!

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.