feat(knowledge-base): follow the convention

[Yougigun]

Because

of consistency with other services

This commit

follows the convention

Note:
this PR is only for POC, and there are some known issues will be refactored soon.

[donch1989]

1. Besides the above comments, for consistency, we should use ListKnowledgeBases and GetKnowledgeBase for our gRPC endpoint naming.
2. How do we handle getting KnowledgeBase from different owners?
3. There are some typos in the PR title and message.

[donch1989]

Hi @Yougigun ,
There are still some design differences compared to other backends. Can you refer to the pipeline or model API design as an example? Keeping the same API design will help clients integrate more easily.

[Yougigun]

Hi @Yougigun , There are still some design differences compared to other backends. Can you refer to the pipeline or model API design as an example? Keeping the same API design will help clients integrate more easily.

@donch1989 Thank you for pointing out.
That's right. I had not noticed the design consistency with other services. Due to mvp testing purposes, I will refactor it in the next version(beta) with @thewbuk

[donch1989]

Hi, @Yougigun
Please write a note in commit message to show that this PR is only for POC, and there are some known issues will be refactored soon.

[Yougigun]

Hi, @Yougigun Please write a note in commit message to show that this PR is only for POC, and there are some known issues will be refactored soon.

done.