Revise ctl-scaffold

[euonymos]

Motivation

Many projects need to implement web API components with CTL that are supposed to be integrated within a website. A simple scaffold example is a must-have thing to promote CTL's usage. I am not sure about preserving other things that were here previously, let's discuss. Our project doesn't require them and I have doubts we can afford re-integrating them back within our budget.

Questions and Tasks

• [ ] Do we need liqwid-nix indeed?
• [ ] Place an actual React app rather than just an empty page
• [ ] Hooks to build and push dist/NPM package?
• [ ] A test-suite example?
• [ ] Back-end service example (or another template for that?)
• [ ] Restore headless browser test suite?

Pre-review checklist

• [x] All code has been formatted using our config (make format)
• [x] Any new API features or modification of existing behavior are covered with tests
• [x] The template (templates/ctl-scaffold) has been updated
• [ ] The changelog has been updated under the ## Unreleased header, using the appropriate sub-headings (### Added, ### Changed, ### Removed, ### Fixed), and the links to the appropriate issues/PRs have been included

[klarkc]

CTL itself should not have a scaffold; I mean, in this repository, it should instead refer to example repositories, like LovelaceAcademy/nix-templates, because you can use CTL in many different ways. Having a scaffold pushes the user to use it in a singular, optioned way that may not match their needs.

[klntsky]

Closing this PR with the motivation stated above