Proposal: v2

[yu-yk]

1. remove redis wrapper, use the redis-go client directly, framework just need to provide some extra function like selecting the correct replica and maybe json decode encode function -> then no need to add new function and update the framework every time when we want to use some new redis function .
2. move every dependencies to the bean object, for example sentry, config, logger, handler, service, repository/model. it makes the structure cleaner and more testable.
3. remove the gorm, just use go-sql-driver and write raw query. We can have more control on what we are doing and easier for code review, because we can see the raw query directly.
4. better error handlings and organizing.
5. eventually maybe we can remove Echo framework as well, now we are just using some middleware and the sentry-echo package. And we also twist and replace a lot of the default echo middleware to fit our use case, we can completely build our own middleware just base on the official golang way.

In this case, the framework should focusing more on the tenant support, and the style can be follow the original golang idioms.
And actually we don't need a complete framework to build the application, we just need some 3rd party router for easy route parsing.