+ Added different heatmaps analytics (for now the replier is implemented)
+ updated utils, removing unnecessary ones and updating method names.
+ added schema for heatmaps data.
+ updated the previous heatmaps to a heatmaps_old name so we could still run analyzer using that. (depricated)
+ commented the `RnDAOAnalyzer` in __init__ but will get it back later with a better name.

moving neo4j utils into its right directory.

+ added author_id filtering too.

it supports both type of emitter and receiver of reply

using the analytics_hourly for all vector analytics.

…understable!

+ couple of small updates on analyzer config custom analytics.
+ updated heatmaps utils class
- the raw analytics of heatmaps is still todo.

and aligning it with its test case.

the analytics should've been giving each engaged user id.

+ fixed: in raw analytics the test cases had some problem (were aligning other users activity in output)
+ fixed: the ActivityType typo fixed.

HeatMapModel is deprecated, will be removed in future.

+ also, updated raw analytics to output a dict rather than python object, so we could later save them in db easily.

+ in order to keep the changes at minimum at possible we're using the previous heatmaps output data schema.
+ but still we're platform agnostic.

+ we needed to update raw data in old test cases to the new format.
+ ignoring the self-interactions now.
+ updated discord analyzer configurations based on discussions.
+ removing the heatmaps_old as was no longer needed.

…red!

this is because for now we know the analyzer won't work so we need to skip a couple of test cases.

+ fixing the problem of credentials passing.

- Removing some other parts of passing connection strings.
- Updated memberactivities to support the platform agnostic's metadata
+ Still interaction matrixes are not updated to use the analyzer config.

+ The interaction matrixes will be using the analyzer config in next commits.

+ the data structures on test cases are updated too.
+ Still more test cases to update.

the new platform agnositc data structure
also, in the period, we should always set hour, minute, second, and microsecond to 0

+ also, cleaning codes with black linter.

…factor

Feat/74 heatmaps agnostic refactor

…sitc

Although the tests are not all passing.

due to code updates

with latest updates on code flows.

updating logs and removing unused codes and files!

fixing codeClimate issues and reducing codeBase size.

+ the automation is still working with discord data and it is not platform agnostic for now.

- The test is still failing but we won't need it in future as analyzer would be a library.

the function names for getting platform data is updated for better code readability.

this will help us to run the CI faster but just for one test case, have to bring docker-entrypoint.sh back to default version after

…form-agnositc

Feat/92 Update analyzer to be platform agnostic!

…form-agnostic

Feat/77 graph analytics platform agnostic

Now the analyzer will accept `platform_id`, `resources`, `period`, `action`, and `window` as input

the function setup_analyzer was deleted and no longer needed.

As we're moving the analyzer to be a library, we're trying to wrap up all the codes in one package.

on test cases rabbitMQ is becoming down and it is always making some test cases to fail.

the AMQP connection is being closed for no specific reason.