fix, allow leap day in schema lines if restriction is entirely in a leap year

Signed-off-by: Sebastian Freundt <freundt@ga-group.nl>
minor, outsource common daisy related funs to daisy.c

Signed-off-by: Sebastian Freundt <freundt@ga-group.nl>
minor, migrate trod.c and schema.c to using daisy.c funs

Signed-off-by: Sebastian Freundt <freundt@ga-group.nl>
revert, allow leap day in schema lines if restriction is entirely in a leap year

Instead we always allow the 29 Feb to be specified but in years with no leap days this will
be mapped to the 28 Feb.

Signed-off-by: Sebastian Freundt <freundt@ga-group.nl>
Merge branch 'fix/leap-years' into next

* fix/leap-years:
  revert, allow leap day in schema lines if restriction is entirely in a leap year
  minor, migrate trod.c and schema.c to using daisy.c funs
  minor, outsource common daisy related funs to daisy.c
  fix, allow leap day in schema lines if restriction is entirely in a leap year
minor, provide regression test for leap year bug

Signed-off-by: Sebastian Freundt <freundt@ga-group.nl>
Merge branch 'test/leap-years' into next

* test/leap-years:
  minor, provide regression test for leap year bug
Merge branch 'next'

* next:
  minor, provide regression test for leap year bug
  revert, allow leap day in schema lines if restriction is entirely in a leap year
  minor, migrate trod.c and schema.c to using daisy.c funs
  minor, outsource common daisy related funs to daisy.c
  fix, allow leap day in schema lines if restriction is entirely in a leap year