Remaining articles cleanup

[amoedoamorim]

Description

• Fixes wrong fragment usage
• Fixes GraphQL warning: description alias used more than once
• Fixes bad propTypes
• Fixes needed key prop
• Fixes unwanted slideout on expand article description
• Deletes unneeded Relay.Container FooterRelay
• Refactors SelectAllTh => SelectAllCheckbox

References: CV2-4047, CV2-4944

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?

Manually

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/)

[caiosba]

Looks great @amoedoamorim , great work on cleaning those up! I added a few comments but they were only "notes" for my own review, no action needed from you. I think you just need to fix unit tests before merging.