fix: make $plugin_dir absolute path

[janaaronlee]

Description

Changed $plugin_dir from relative path to absolute path.

Motivation and Context

Recent changes in asdf-direnv broke compatibility with asdf-gcloud. Whenever direnv tried to load gcloud, it would display the following error:

direnv: using asdf gcloud 392.0.0
direnv: loading ~/.asdf/plugins/gcloud/bin/exec-env
./exec-env:9: ./lib/utils.bash: No such file or directory

Changing $plugin_dir from relative path to absolute path in exec-env fixes this issue.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Usage examples

Same as before.

How Has This Been Tested?

Checklist:

• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[nklmilojevic]

This PR also solves this #64

[jthegedus]

Hi all, thanks for the feedback. I am going to merge this. I am still not sure why this is needed here and not for all other plugins. Nor do I like the fact it does a cd subshell where previously things have worked fine. I don't use asdf-direnv and don't want to go down the investigation rabbit hole. Thanks again, lets hope this fixes all for everyone.