6.0.0
fix: typo in comment.
fix(visualMap): fix some text style can't work on visualMap
chore: remove unused types
Merge remote-tracking branch 'origin/v6' into feat-matrix-enhance
feat(matrix & calendar): (1). Support matrix col/row size option. (2). Support corner content options in matrix. (3) Support body content options. (4). Support matrix `mergeCells`. (5). Fix and refactor the matrix style options, conserning their inheritance and z-order and flexibility. (6). Support declaratively layout other components (including grid/polar/geo/graph coord sys, and dataZoom/visualMap/legend/... components) based on `matrix`/`calendar`. And and enhance the echarts API `convertToLayout`/`convertToPixel`, custom series API `api.coord`/`api.coord` to support this feature comprehansively. Considering the previous "pie layout on coord sys", introduce the `boxCooridnateSystem` and `createBoxLayoutReference` to all of the components and echarts for the overall coord sys infrastructure. (7). Add some test cases to matrix and calendar.
refact: put all core modules in the core dir. only do export in lib/echarts
fix: not install directly to avoid installed twice.
refact: make components installable
fix(type): optimize types for dts bundling
add axis model creator type
**There are these issues existing before this commit:** (1). If no dimensions specified on dataset, series can not really share one storage instance. (Because the each series will create its own dimension name (like ['x', 'y', 'value'], ['x', 'value', 'y'], and the storage hash is based on those names. So the hash can not match). (2). Each time `setOption` update series (but not change `dataset`), new data stack dimensions (and corresponding chunks) will be keep added to the shared data storage, and then the chunks will be more and more. (3). When "unused dimension omit" happen, the index of SeriesData['dimensions'] and SeriesData['getDimension'] is not the dimensionIndex that users known. But there are someplace still use dimensionIndex to visit them. (especially in visualMap and other similar cases that user can input dimension index via option). (4). If user only specify type but no name in dimensions, their will be some bug when "unused dimension omit" happen. (Because unused dimensions will not auto-generate dimension name by `createDimensions` and so that it has no dimension name in storage, and can not be queried by dimension name). (5). If different series option specify its own `dimensions` but share one `dataset`, the `source` get by `sourceManager` is different `source` instances in each series. Those `source` instances contain different `dimensionDefine` but reference the same data. And then a data storage created by based on s
refact: fix bugs caused by the refactor. export types