feat: make some function deprecated

[zong-zhe]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

[coveralls]

Pull Request Test Coverage Report for Build 8476961753

Details

• 30 of 64 (46.88%) changed or added relevant lines in 7 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.4%) to 43.257%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pkg/cmd/cmd_add.go	0	1	0.0%
pkg/cmd/cmd_pkg.go	0	1	0.0%
pkg/api/kpm_pkg.go	3	5	60.0%
pkg/cmd/cmd_graph.go	0	2	0.0%
pkg/cmd/cmd_push.go	0	2	0.0%
pkg/client/client.go	26	52	50.0%

Totals
Change from base Build 8467230085:	0.4%
Covered Lines:	1931
Relevant Lines:	4464

---

💛 - Coveralls

[Peefy]

I have some suggestions for this PR

• Write clearly what are the current issues with the API, goals and non-goals
• How to connect different APIs in user scenarios, i.e. demand and user stories
• What APIs do we need to provide for the problems and requirements, what are the levels of APIs, how to distinguish their names, and some specific prompts
  • How to distinguish whether to instantiate kpm client
  • How to distinguish the APIs of kpm and kcl-go
  • Can I directly obtain the usage of the API based on its name