API Change / Migrate harvester Jeeves services to Spring MVC

[josegar74]

Migrate the following harvester Jeeves API services to Spring MVC:

• Clear
• Create clone
• Get
• Invoke
• Remove
• Run
• Start
• Stop
• Harvester log file
• History delete: the original service contains code to delete the harvester history by harvester uuid, which is used by the UI and it has been migrated. But also has some code that accepts a list of harvester ids and a list of files (I guess log files?), that seem not used anywhere in the UI. This code hasn't been migrated.

core-geonetwork/harvesters/src/main/java/org/fao/geonet/services/harvesting/HistoryDelete.java

Lines 76 to 102 in 59762eb

	Collection<Integer> ids = Collections2.transform(params.getChildren("id"), new Function<Object, Integer>() {
	@Nullable
	@Override
	public Integer apply(@Nonnull Object input) {
	return Integer.valueOf(((Element) input).getText());
	}
	});
	List<Element> files = params.getChildren("file");
	for (Element file : files) {
	try {
	File f = new File(file.getTextTrim());
	if (f.exists() && f.canWrite()) {
	if (!f.delete()) {
	org.fao.geonet.utils.Log.warning(Geonet.HARVESTER,
	"Removing history. Failed to delete file: " + f.getCanonicalPath());
	}
	}
	} catch (Exception e) {
	org.fao.geonet.utils.Log.error(Geonet.HARVESTER, e.getMessage(), e);
	}
	}
	if (!ids.isEmpty()) {
	nrRecs = historyRepository.deleteAllById(ids);
	}

Also the service deletes the entries in the database, but doesn't seem to delete the log files associated with the harvester. I'm not really sure if should be deleted also.

Jeeves services are mark as deprecated.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}