[2.0.0] Rename Config to CacheManagerConfig

## 🏗 Enhancement Proposal

Since version 2.0.0 the flutter_cache_manager exports a class called `Config`. This name is very general and causes problems in all my projects because I have a general Config class.

I think the name `Config` is a very bad choice, as it is way to general. So I propose renaming it to `CacheManagerConfig` to prevent conflicts like these to occur.

I know that it is possible to work around this issue by using `import a as b`, but I think this should be avoided to make the development process more easy.

Also the name `CacheManagerConfig` would be much more intuitive to use, as you usually wouldn't expect to have a class called `Config`, but rather somthing like `CacheManager***` while writing your code with intellisense.

首先定位 flutter_cache_manager 中导出的 Config 声明及其所有引用。在决定重命名范围之前，检查该 package 现有的测试和公共 API 入口；当所请求的名称 CacheManagerConfig 得到一致使用且受影响的测试通过时，即表示完成。

由索引模型根据 Issue 内容生成。