Decouple the generation of settings.js from update-attack.py

The main Pelican build process generates a file called settings.js which includes three vars:

var base_url = “/“;
var build_uuid = “5144be18-993a-4aa4-bb2e-124dd2ce41b8”;
var tour_steps = {‘matrix’: ‘matrices/enterprise’, ‘technique’: ‘techniques/T1548’, ‘subtechnique’: ‘techniques/T1548/002’, ‘relationships’: {‘step3’: [‘T1003-004’, 5], ‘step2’: [‘T1555’, 3], ‘obj_id’: ‘software/S0349’}};

Two of these vars, base_url, and build_uuid are used by the search module.

The search module should be capable of generating or referencing these vars independently. We need to devise a solution that decouples these vars from the Pelican build process.

Start by tracing how the Pelican build process and update-attack.py produce settings.js, then inspect how the search module reads base_url and build_uuid. Define an approach for generating or referencing those variables independently of the build process. Done means the search module no longer depends on settings.js being generated by the Pelican build.