When storing HCM module sequence number in baseline, JCR-encode module full name

ConfigurationBaselineService.updateModuleSequenceNumber() should JCR-encode the module full name when converting it into a JCR path in the baseline, using the same NodeNameCodec.encode() call that the main updateBaselineModules() method uses. Otherwise, a module name containing reserved JCR characters (like '/') could break bootstrap behavior.