Revisit the implementation of typename: more customizable and stable.

[sighingnow]

What do these changes do?

Revisit the vineyard::type_name implementation to make it more composable and stable when acrossing platforms. e.g., std::string will be always std::string no matter on which platform, and int64_t will be always "int64", rather than "long", or "long long" on different platforms.

Users can supply their own typename for customized type, e.g.,

struct XX {
};

namespace vineyard {

template <>
inline const std::string type_name() {
    return "XX-name";
}
}

Related issue number

Fixes #457

[codecov]

Codecov Report

Merging #472 (9dfcd93) into main (9aed745) will increase coverage by 0.13%.
The diff coverage is 88.00%.

@@            Coverage Diff             @@
##             main     #472      +/-   ##
==========================================
+ Coverage   70.03%   70.16%   +0.13%     
==========================================
  Files          63       63              
  Lines        5589     5614      +25     
==========================================
+ Hits         3914     3939      +25     
  Misses       1675     1675              

Impacted Files	Coverage Δ
src/common/util/typename.h	88.00% <88.00%> (+88.00%)	⬆️
src/server/async/socket_server.cc	70.51% <0.00%> (+0.49%)	⬆️