Feature/4936 4937 analytics dashboard foundation

[amoedoamorim]

Description

• QueryRenderers for Articles Dashboard and Tiplines Dashboard
• Basic page layout for both pages
  • Shared CSS module for both pages
  • Filter header area
    • Reusable filter components
      • TimeFrame
      • Languages
      • Platforms
  • 2 column layout
• Add charts in each page with no data/empty states while GraphQL layer is being worked on
• Connect GraphQL data to charts
• Connect filter components to query for both pages

References: CV2-4936 CV2-4937

Type of change

• Performance improvement and/or refactoring (non-breaking change that keeps existing functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Security mitigation or enhancement
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Automated test (add or update automated tests)

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can verify the changes. Please describe whether or not you implemented automated tests.

Things to pay attention to during code review

Please describe parts of the change that require extra attention during code review, for example:

• File FFFF, line LL: This refactoring does this and this. Is it consistent with how it’s implemented elsewhere?
• Etc.

Checklist

• I have performed a self-review of my own code
• I've made sure my branch is runnable and given good testing steps in the PR description
• I considered secure coding practices when writing this code. Any security concerns are noted above.
• I have commented my code in hard-to-understand areas, if any
• I have made needed changes to the README
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• If I implemented any new components, they are self-contained, their propTypes are declared and they use React Hooks and, if data-fetching is required, they use Relay Modern with fragment containers
• If my components involve user interaction - specifically button, text fields, or other inputs - I have added a BEM-like class name to the element that is interacted with
• To the best of my knowledge, any new styles are applied according to the design system
• If I added a new external dependency, I included a rationale for doing so and an estimate of the change in bundle size (e.g., checked in https://bundlephobia.com/)
• If I touched a file that included an eslint-disable-file header, I updated the code such that the disabler can be removed