Distrobuilder support

#### Community Note

Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

#### Description

Using distrobuilder or something based on the internals of distrobuilder to build LXC images.

#### Use Case(s)

As per LXC documentation, using LXC templates the way it currently seems this plugin is doing is not recommended, and doesn't work very well. Getting LXC Templates to run is not very easy, and in some cases (all my attempts with alpine linux) it doesn't work at all. The official way to do it instead is to use distrobuilder, which constructs a rootfs for the image that can be used to spawn an lxc container from, using the rootfs as a starting point. This would make building lxc containers easier, and wouldn't require having a working LXC template script for each distro, but just the download sources.

#### Potential configuration

This could be done by using the shared package of the distrobuilder package to download the base rootfs, which can then be used to start up an lxc container, which can then function as it currently does

#### Potential References
https://github.com/lxc/distrobuilder

https://linuxcontainers.org/distrobuilder/introduction/

No files, tests, or entry points are named. Start by reading the repository's current LXC image-building implementation and the referenced distrobuilder documentation, then determine how its rootfs workflow would fit the plugin. Done should mean that LXC images can be built through distrobuilder or its shared package instead of relying on LXC templates.

Written by the indexing model from the issue text.