Issue 3983: Avoid define-public and define*-public with curried definitions

Issue 3983: Avoid define-public and define*-public with curried definitions

Regarding curried definitions, GUILE has problems with define-public
before version 2.0.10, and with define*-public even later.

define-safe-public is implemented by LilyPond itself rather than the
(ice-9 curried-definitions) module and is unproblematic.

This is basically a cop-out since juggling with overriding bugfix
definitions of define-public is a distraction for getting GUILEv2
migration under way that we can do without.