Review the ESLint config and see if it can be made stricter (eg. adding whitespace rules), to ensure code gets more consistent. Our current config was configured before we started adding React to the frontend, so it may require some additional work. 

Tasks

• Determine if this requires an ADR first. If so follow the steps described below and defer the rest of the tasks to a follow-up implementation ticket.
• Adjust CI config to lint all js code (currently only checks public/*.js)
• Adjust our blocks js code to meet current eslint configuration. If it turns out to be too many code changes per block, create subtasks.
• Adjust eslint config to be more strict to enforce the rules we already apply

ADR Tasks (if needed)

• Refine the ADR to reach a "proposed" status.
• Request for comments on the dev channel.
• Address or integrate comments where applicable.
• Bring the ADR for discussion in the next Refinment session.
• Open implementation tickets once ADR has reached "decided" status.