Shim SILE.types

[Omikhleia]

See https://github.com/sile-typesetter/sile/issues/2053#issuecomment-2158395193

• [ ] Add a silex.types compatibility layer (see below SILE.types scoped objects in SILE), as we had done in advance for SU.ast
• [ ] Make a silex.sile minor release
• [ ] Go one by one on each of our xxx.sile module to upgrade their code
  • Todo : list here each module as analyzed, fixed and released
• [ ] Perform non-regression testing with SILE 0.14 (expecting no issue)

So the 0.14-based workflow of my current book projects still works but all modules are prepared for 0.15 (and we'll need testing them with 0.15 but the code should already have been updated -- and we'll have that part behind us if any problem occurs).

Food for though (from @alerque 's script):

s#\bSILE.color\b#SILE.types.color#g
s#\bSILE.colorparser\b#SILE.types.color#g
s#\bSILE.length\b#SILE.types.length#g
s#\bSILE.measurement\b#SILE.types.measurement#g
s#\bSILE.nodefactory\b#SILE.types.node#g
s#\bSILE.units\b#SILE.types.unit#g

I don't think my code base uses those below (as far as I remember), but also to check:

s#\bSILE.paperSizeParser\b#SILE.papersize#g
s#\balignright\b#raggedleft#g

[Omikhleia]

It's a lot of work for something that does not bring better typography, and is not even perfect.

I could simplify my workflow a lot by removing all my .sile modules from the SILE ecosystem, and bring them all back under the umbrella of the resilient collection.