Improve function calling (close #279)

[forever-ly]

Description

As metioned in [#279](https://github.com/camel-ai/camel/issues/279), the parsing of functions relies on specific annotation styles(Google-style). To support a wider range of docstring styles, , I have reimplemented the function camel.utils.functions.parse_doc by introducing docstring_parser package(https://pypi.org/project/docstring-parser/) after disscusing with [@lightaime](https://github.com/lightaime). Currently version supports ReST, Google, Numpydoc-style and Epydoc docstrings.

Motivation and Context

close #279

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds core functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Documentation (update in the documentation)
• [ ] Example (update in the folder of example)

Checklist

Go over all the following points, and put an x in all the boxes that apply. If you are unsure about any of these, don't hesitate to ask. We are here to help!

• [x] I have read the CONTRIBUTION guide. (required)
• [ ] My change requires a change to the documentation.
• [x] I have updated the tests accordingly. (required for a bug fix or a new feature)
• [ ] I have updated the documentation accordingly.

[Wendong-Fan]

hey @Billy1900 @FUYICC ,

Just noticed this is the old PR, the latest one is https://github.com/camel-ai/camel/pull/393 Please review the latest one if you have time, I will close this PR directly and sorry for the confusion

[lightaime]

Closed since this is a duplicated with https://github.com/camel-ai/camel/pull/393.