Activate cloud plugins explicitely

[rdettai]

Change described in https://app.shortcut.com/tenzir/story/36533/fix-the-way-cloud-plugins-are-loaded

📝 Reviewer Checklist

Review this pull request by ensuring the following items:

• All user-facing changes have changelog entries
• User-facing changes are reflected on vast.io

Reviewer instructions

• Start by checking out the documentation update
• The main.py contains the new plugin loading logic, so it is a good starting point for the code review itself
• The core deploy, deploy-step, destroy and destroy-step methods are now fit to deploy/destroy any module, so we removed the module_name.deploy and module_name.destroy commands in modules such as flowlogs and cloudtrail

[rdettai]

Starts off #2473, so requires it to be merged first

[rdettai]

https://github.com/tenzir/vast/actions/runs/2883267769

[rdettai]

https://github.com/tenzir/vast/actions/runs/2917862379

[kaansk]

Apart from this review, we can discuss about many readme.MD and other documentation files under different folders which makes it really hard to follow. We can just have 1 documentation file including everything.

Additionally, the .env.example template should have following keys as well. These are referenced in aws-pro and can cause confusion.

VAST_PEERED_VPC_ID=
VAST_CIDR=
VAST_AWS_REGION=
VAST_CLOUD_PLUGINS=
VAST_VERSION=
VAST_IMAGE=

[kaansk]

I was able to initialize and destroy pro environment. The issue with environment variables documentation will be followed in another story.

I commented on changelog entry for a typo.

[rdettai]

@kaansk I addressed you request and created a separate internally tracked issue for env variable template.