Using the ResultProperties class will permit generation and UI
separation (eg in visibility toggling/grouping) of different dice
variants.

In practice, this means mostly changing

rollstats.xyz
 to
resultPorperties.rollstats.xyz

in the generation functions.

Changes to permit dice variations from the frontend to Asphodice class,
successCutOff in particular

Uses default Asphodice class, rolls sets of 1..10 dice 100000 times for
stats.

Future work will need minor extensions of base Asphodice class, such as:
	- class short name (for HTML element ids)
	- class description (to explain what mechanics are implemented-
	  eg different successCutoff)

FE will also need adapted:
	- ids will need to use class short names (as above)
		- result cards
		- chart canvases
		- tables
	- anchors for 'jump to' navigation (see next item)
	- grouping of dice class results with show/hide groups (or
	  tabs or some other means of selecting results, eg dropdown), eg:
		- Asphodice
			- d=1
			- d=2
			- ...
			- d=10
		- AsphodiceCutoff8
			- d=1
			- d=2
			- ...
			- d=10
		- AsphodiceCrits
			- d=1
			- d=2
			- ...
			- d=10
		 (etc)

Also include bootstrap.js to make collapsing actually work, and change
order of links in head to ensure js is included in the 'correct' order

Is it less monolithic? Yes
Is it actually any better? Uhh

This is still doing some reasonably code-smelly things which could
probably be improved with a decent JavaScript templating engine, but:

- it's after 10PM on a SAturday night and I've been working on this all
  afternoon
- it works for now
- I don't want to go too far down the rabbit hole of super-polished code
  (hah!) before I check that the output format suits C

It is actually better in the sens that we present charts first (easier
to see at a glance) with their data below them.

Todo:
 - sort output of outcomesBalance for chart (already sorted for table)
 - hide/show toggles
 - make the doughnut chart more straightforward (swap legend order,
   rename labels)

This is still pretty quick and dirty, with lots of refactoring and
general tidying up ahead; but it gives an example structure to start
from

Emphasis on the dirty, not so much 'quick' ! This shows select outputs
from the default Asphodice class:
 - rerolls
 - outcome balance
 - outcomes

This information is presented in a Bootstrap card:

https://getbootstrap.com/docs/5.0/components/card/

In dev mode this means changes to ts files can now be watched
live.

Can now build all with 'gulp' (if gulp-cli installed)

Big commit. Breakdown:
 - .gitignore includes gulpfile.js (otehrwise excluded)
 - gulpfile sets up build steps + browsersync
 - src/ files for FE (stub for now)
 - moved ts to src/ for consistency
 - update tsconfig with new paths
 - package.json lists new reqs

Cancels out 10s and 1s, for use in rerollNeeded()

Aids unit testing which is needed for good practice and as we
are seeing bugs creep in around unnecessary rerolls

Also start sketching out results set for aggregate results