Do we need a block config?

In `scripts.js`, there's a selector block config with paths, script and style filenames. It allows loading a block for any element matching the selector, and avoids loading non-existent files (e.g. if a block only consists of a CSS file).

But it also adds complexity, reduces modularity (blocks need to be registered in `scripts.js`), which requires a trade-off.

Start by reading scripts.js and trace the selector block config, including its paths and script and style filenames. Evaluate the stated benefits of loading only existing files against the added complexity and reduced modularity. Done means reaching and recording a decision on whether the block config should remain.

Written by the indexing model from the issue text.