Move Nunjucks Logic from Frontend to Backend

[ShaanCoding]

Feature Details

As a software developer I want to move the Nunjucks rendering logic from the components located in the frontend, to instead the backend, so that I can have better maintainability of our application as well as improve our performance

Cover any details here, e.g. feature number and stakeholders

Expected Functionality

• Move nunjucks rendering logic from frontend to backend
• Allow backend API route to accept list of components as well as the variable data and reply with the markdown layout to render
• Add debouncing on the API call instead of onChange to save on network requests
• Replace useEffect with T3/react-query on API calls so that it is responsive

[ShaanCoding]

Not sure on this one as it keeps server fees very low / almost free with caching. Will tackle later

[ShaanCoding]

Whilst the way I'm doing it isn't ideal, it'll save on a lot of expensive computations, keeping loads low through caching. Not planned