Add scaffolding for CompleteStartedTask implementation in matching

[fimanishi]

What changed?
Added scaffolding for the new IDL CompleteStartedTask implementation in matching. This endpoint will be called by the history service in order to complete a task in matching after it has been replicated in history.

Why?
This will allow cadence to actively delete stale tasks from matching on the passive side as these tasks are processed on the active side and replicated, avoiding the large passive side partitions and reducing task processing latency after a failover How did you test it?
This implements only the scaffolding. No logic present.

Potential risks

Release notes

Documentation Changes

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 25 lines in your changes missing coverage. Please review.

Project coverage is 72.98%. Comparing base (c0cd4c5) to head (e4c4104).
Report is 5 commits behind head on master.

Files	Patch %	Lines
common/types/mapper/thrift/matching.go	0.00%	10 Missing ⚠️
common/types/mapper/proto/matching.go	0.00%	9 Missing ⚠️
service/matching/handler/engine.go	0.00%	3 Missing ⚠️
service/matching/handler/handler.go	0.00%	3 Missing ⚠️

Additional details and impacted files

Files	Coverage Δ
common/types/matching.go	0.00% <ø> (ø)
service/matching/handler/engine.go	79.89% <0.00%> (-0.31%)	⬇️
service/matching/handler/handler.go	98.67% <0.00%> (-1.33%)	⬇️
common/types/mapper/proto/matching.go	92.91% <0.00%> (-2.44%)	⬇️
common/types/mapper/thrift/matching.go	95.34% <0.00%> (-3.85%)	⬇️

... and 14 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0cd4c5...e4c4104. Read the comment docs.