fix symlinks in `setupWorkspace.sh` scripts used by published automation

The `setupWorkspace.sh` script copies the latest workspace to `/workspaces/current` and moves the old `/workspaces/current` folder to a timestamped version any time you run it. If you cd into one of the older ones, and attempt to execute terraform commands, it will fail b/c the symlinks were generated are linked to the absolute path of `/workspaces/current/terraform.tfvars` which will have changed since you’re no longer in the current directory. In my case, I had fs cloud automation, then i ran turbo automation… they used the same container image, but turbo was in /workspaces/current . when i went back to fscloud to rebuild my cluster (make it bigger), the terraform failed until i updated all of the symlinks

Impacted repos:
- https://github.com/cloud-native-toolkit/automation-solutions
- https://github.com/ibm-ecosystem-lab/ibm-cloud-reference-architectures/
- https://github.com/orgs/IBM/teams/ecosystem-labs/repositories