Update Features with a fallback logic to install previous version if the "latest" tags are missing artifacts

[samruddhikhandale]

We saw #888 where git-lfs Feature builds were failing as the latest tag available is 3.5.0, however, the corresponding releases are still not available. #894 added a fallback logic.

We already updated few Features with this fallback logic, however, we need to add this for all the Features in https://github.com/devcontainers/features

Note: Only add fallback logic if following conditions are met

1. If the requested version is latest
2. find_version_from_git_tags is used to find the latest version

Gaurav Saini (@gauravsaini04) Feel free to create sub-issues if needed, also, creating separate PRs for each Features would be appreciated.

[gauravsaini04]

Hi Samruddhi Khandale (@samruddhikhandale) , found a similar scenario in docker-outside-of-docker feature, so did create a sub issue and raised PR #901 for this.

[gauravsaini04]

Have created many sub issues for this issue in issue 145 of internal. Kindly check and approve those that need to be processed.

[samruddhikhandale]

#911 (comment) is a great early feedback. Would be good to update the fallback logic according to this.

[gauravsaini04]

pls check pr #914

[gauravsaini04]

So now only the node feature's, nvm pkg installation - fallback implementation is left.
Few tests are failing in it that point towards installation of pnpm pkg with node v16 that's currently getting installed in failing scenarios like centos-7 & install_node_16_on_bionic. They need at least a node v18 for it to get installed properly.
👍

The feature's that have working fallback method implemented for them are listed below :

1. PHP
2. Powershell
3. Python
4. Ruby
5. Terraform
6. Docker-In-Docker
7. Docker-Outside-Of-Docker
8. git-lfs
9. github-cli
10. kubectl-helm-minikube

[gauravsaini04]

work on node - nvm feature will remain on hold for the moment