Providers: Fix init with broken link in plugin_cache_dir

[Filirom1]

Hello

Fixes #27445.

Instead of raising and error, it display a warning (TF_LOG=trace) and continue analyzing the next providers.

Cheers
Romain

[hashicorp-cla]

All committers have signed the CLA.

[codecov]

Codecov Report

Merging #27447 (5ae5c99) into master (5132abf) will increase coverage by 0.00%.
The diff coverage is 0.00%.

Impacted Files	Coverage Δ
internal/getproviders/filesystem_search.go	63.20% <0.00%> (-0.51%)	⬇️
internal/providercache/dir.go	73.46% <0.00%> (+6.12%)	⬆️

[pselle]

I'm approving this but I'd like to request a second opinion from another Core team member.

Having run into this today because I'd messed with my settings to replicate the reported issue, I have a better understanding now that the scanning failing init completely, and opaquely, when installing another provider, is difficult and unhelpful. (in this case where I was replicating, it was trying to install an AWS provider, but I'd messed with my plugin-cache dirs for the purpose of recreating this issue, and it was confusingly failing)

Another comment on the initial report #27445 (comment) has a helpful context of how this can happen in real-world cases.

Requesting second opinion because I'm not well-familiar with the plugin installer and cache processes.

[mildwonkey]

🎉 thank you, this has been driving me crazy 😂

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.