Add support for custom ROBOT plugins in Makefiles

[matentzn]

Introduced new Makefile rules to manage ROBOT plugins, including installation of custom and supplementary plugins. Added targets for simple merge operations and an obsolete replacement test using the odk plugin in mondo.Makefile. These changes improve plugin management and extend ontology processing capabilities.

[matentzn]

@ptgolden is PR is a precursor for adding the updated sssom-java into the Mondo pipeline. This is only necessary while we do not have an ODK minor release, but it is necessary so we can move forward.

Unfortunately Mondo, the most important ontology in my portfolio, is xactly the only ontology that has not been migrated to a proper ODK setup where all of this is automated.

[twhetzel]

@matentzn do you want me to review or @ptgolden?

[matentzn]

@twhetzel you if possible - my comment was only to avoid duplicative work from @ptgolden who needs this here to finish his current task.

[twhetzel]

Where is the odk.jar coming from?

[ptgolden]

I believe the right thing here is to do the same as the SSSOM plugin:

$(ROBOT_PLUGINS_DIRECTORY)/odk.jar:
	curl -L -o $@ https://github.com/INCATools/odk-robot-plugin/releases/download/odk-robot-plugin-0.3.0/odk.jar

[twhetzel]

Consider having obsolete-replace-test depend on extra_robot_plugins.

[twhetzel]

remove trailing \

[twhetzel]

The rule silently succeeds even if the source file doesn't exist. Add an else clause to fail explicitly when the source file isn't found.

[twhetzel]

The overall idea makes sense, but there are spots that would benefit from updates.

[ptgolden]

A general question here. In the past when adding custom ROBOT plugins, I've made an addition in the ODK configuration file, e.g.:

robot_plugins:
  plugins:
    - name: odk
      mirror_from: https://github.com/INCATools/odk-robot-plugin/releases/download/odk-robot-plugin-0.3.0/odk.jar

I've noticed the Makefile in Mondo is not driven by a configuration file, and it also differs significantly from the template in the current release of ODK (since it hasn't been maintained by running ./run.sh odk.py). My hunch-- tell me if I'm wrong-- is that this repository predates that workflow.

(Answering my own hunch: yes, it seems that this repo's Makefile derives from ontology-starter-kit in September 2017 at bcc59a0, and the YAML-driven generation only came with INCATools/ontology-development-kit@556ce6d in November 2018)

Would it be at all worth the effort in the medium term to migrate to the YAML configuration format and move all custom functions into mondo.Makefile?

For the purposes of this commit-- yes, this all looks good, given that it's copied from the current ODK template and that is known to work. If I'm added as a reviewer, I'm happy to approve.

[ptgolden]

Oh, I should have read the beginning of this issue more closely after my detective work:

Unfortunately Mondo, the most important ontology in my portfolio, is xactly the only ontology that has not been migrated to a proper ODK setup where all of this is automated.

[matentzn]

@ptgolden please take over this PR and do with it as you see fit.