WIP: Label Breakdown api

[g1nt0ki]

This PR includes a bunch of small refactors and optimizations, but major change is pulling dimension fee breakdown (by custom label) and exposing it via api:

• add pro routes
• add versioning and new route pattern for dimensions, should be extended to other metrics
• added cache object structure to types.ts
• transform records immediately after pulling from db, this way we dont repeat the transformation and the same record everytime we run the cron job, downside of this is, we need to reset cache if we change the transformation
• removed some unused code blocks/files
• added (simple) compression & decompression logic while writing/reading cache, and split cache by adapter type, this way, it will take longer to hit the file size limit
• moved some parts of the code out of cron/dimensions.ts to make the file look (little) less daunting, added more comments
• I replaced aggregated from dimensions record with aggObject, I had a good reason, but cant recall why now, think I probably tried to remove it, but realized that if record contains non dataType fields, makes bit more of of a pain to iterate, right now, we know that all keys in aggObject are dataType (like dailyFees, dailyRevenue, etc)

What is missing/needs to be fixed:

• need to include breakdown methodology
• derive labels from breakdown methodology matching given dataType, if not matching key in given adapter, else global breakdown dictionary
• merge label data for parent protocol and verify that this works
• check with mint & integrate in the UI

[0xpeluche]

There was some confusion here, I guess →

const validMetricTypesSet = new Set(Object.values(AdapterType)) as Set<string>
const validRecordTypesSet = new Set(Object.values(AdaptorRecordType)) as Set<string>

[g1nt0ki]

ah, good catch

[0xpeluche]

The PR looks good to me, I didn’t see any blocking code or errors. Locally, the API works and correctly returns the methodologies on the pro routes.
However, I just noticed a small mistake that I hadn’t caught in my previous review

defillama-server/defi/src/api2/routes/dimensions.ts

Lines 47 to 50 in 7f47751

	if (!isSummary) {
	const protocolName = req.path_parameters.name?.toLowerCase()
	return { adaptorType, dataType, excludeTotalDataChart, excludeTotalDataChartBreakdown, category, fullChart, protocolName }
	}

→ You need to add includeLabelBreakdown, otherwise the pro routes won’t include the labelBreakdown data

return { adaptorType, dataType, excludeTotalDataChart, excludeTotalDataChartBreakdown, category, fullChart, protocolName, includeLabelBreakdown }