Plugin simple connector

[ale8k]

Description

This is a WIP and example of how we may want to structure a jujuclient wrapper. We need a way to mock the clients and I tried my best thinking of sensible solution such as... NewClient(...options) or Client.WithController(a).WithController(b).

In the end, it felt almost inevitable to return the interfaces.

Next, I thought about generating the interfaces, and had a lot of success

output_package="jujuclient2"
path_to_pacake="./internal"

for dir in modelmanager cloud controller applicationoffers; do
    find ./vendor/github.com/juju/juju/api/client/$dir -type f -name '*.go' | while read -r file; do
        base_name=$(basename "$file" .go)
        
        interface_name="${base_name^}Client"
        
        output_file="$path_to_pacake/$output_package/${interface_name}.go"
        
        echo "Processing: $file -> Interface: $interface_name -> Output: $output_file"
        
        ifacemaker -f "$file" -s Client -i "$interface_name" -p "$output_package" -o "$output_file"
    done
done

But then it occured to me this may appear confusing in the long run as to what methods are actually used within JIMM. I ultimately thought having the interfaces split, but only contain what JIMM actively requires was best.

Overall, let me know what you think on this approach and if good enough - let's try replace the Dialer.