Implement the tool registry in the piped side

[Warashi]

What this PR does:

as title

Why we need it:

We decided the installation tools should be done on the piped side, not the plugin. ref; #5218

Which issue(s) this PR fixes:

Part of #4980

Does this PR introduce a user-facing change?: No

• How are users affected by this change:
• Is this breaking change:
• How to migrate (if breaking change):

[codecov]

Codecov Report

Attention: Patch coverage is 48.64865% with 57 lines in your changes missing coverage. Please review.

Project coverage is 25.38%. Comparing base (23eddac) to head (f9f7bf0).
Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
pkg/app/pipedv1/cmd/piped/grpcapi/tool_registry.go	65.06%	21 Missing and 8 partials ⚠️
pkg/app/pipedv1/cmd/piped/grpcapi/plugin_api.go	0.00%	22 Missing ⚠️
pkg/app/pipedv1/cmd/piped/piped.go	0.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5343      +/-   ##
==========================================
+ Coverage   25.29%   25.38%   +0.09%     
==========================================
  Files         444      445       +1     
  Lines       47656    47772     +116     
==========================================
+ Hits        12053    12126      +73     
- Misses      34661    34696      +35     
- Partials      942      950       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[khanhtc1202]

Since the tool is not plugin-specific, I think we should have some kind of cache to avoid redundant installation. If the name and version are the same, then we should return the installed path immediately instead of running the script, wdyt?

[Warashi]

I agree. I'll add the cache like below.

pipecd/pkg/app/piped/toolregistry/registry.go

Lines 116 to 121 in 23eddac

	r.mu.RLock()
	_, ok := r.versions[name]
	r.mu.RUnlock()
	if ok {
	return path, false, nil
	}

[Warashi]

@khanhtc1202
fixed on this commit, thanks
75d7daa

[ffjlabo]

[Ask] Is it enough just to create the tmp dir for the tool installation in the newToolRegistry.

[Warashi]

Do you mean to call like os.MkdirTemp("", "tool-registry") and do not pass the tmpDir as the argument?

[ffjlabo]

Yes, I mean fixing as newToolRegistry(toolsDir string) and call os.MkdirTemp inside it as you said.

[Warashi]

I got your point! That's enough.
I'll change the codes.

[Warashi]

fixed on this commit
f9f7bf0

[ffjlabo]

LGTM

[khanhtc1202]

Good to go 👍