AWS all-checks command ignores pmapper-data-basepath

[manotux]

Description of Bug

When running single AWS commands that relies on PMapper data, as for example "pmapper" and "cape", the folder indicated on --pmapper-data-basepath is considered and files found. However, when using the "all-checks" command the parameter appears to be ignored and the following message displayed in the output:

[pmapper][non-prod] No pmapper data found for this account. 
                        1. Generate pmapper data by running `pmapper --profile non-prod graph create`
                        2. After that completes, cloudfox will attempt to enrich this command and others with pmapper privesc data

I'm running Cloudfox on a Kali VM and as a workaround I had to create a symlink from ~/.local/share/principalmapper to the actual folder containing pmapper data.

Not sure if this is the root cause, but I was able to verify that function generatePmapperDataBasePaths defined in file aws/shared.go seems to only look for files under XDG_DATA_HOME and folder mentioned above

What should the expected behavior be

Folder indicated to parameter --pmapper-data-basepath be considered for the "all-checks" command.

Steps to Reproduce

Running against a list of accounts with profiles defined on accounts.txt file:
$ cloudfox aws -l accounts.txt --pmapper-data-basepath ./pmapper/ all-checks

Additional context

Kali Linux, version 1.15.0