New action for D4science storage interaction with d4storagehub4R package

[abennici]

Add a new action using eblondel/d4storagehub4R services to create folders and upload of out files on D4Science Workspace directory.
This action should manage at least :

• connection to folder if existing
• creation of folders if missing
• upload of file handled in entity$data$uploadSource
• fetch the public link of the newly uploaded file and enrich entity$relations with it
• manage option depositWithFiles to upload all data/metadata resources

Some brainstorming is required on:

• how/where the workspace folder path should be coded. As 1st requirement, a workspace property should be part of the d4storagehub software declaration. A 2d requirement, there is a need to refactor the workspace entity data property (Need to refactor workspace in relation with its target software #155), as a similar concept could be targeting 2 different software, and create a conflict. Example: a Geoserver workspace named 'my_workspace', and a D4Science workspace folder named 'my_folder'.
• re-executing the action at the end of the workflow similarly to zenodo/dataverse in case the user wants to upload more resources (all, data, metadata). To be done in link with action options
• the position / order of the action within the list of actions to be executed. If the file upload is performed before an action such as geometa (ISO 19115), it offers the possibility to enrich the metadata with a web-link from D4Science. Reversely, if this file upload occured after geometa (ISO 19115), we lose the capacity to enrich the ISO 19115 with a D4Sscience web-link. By analogy, we have the same issue with Zenodo action that needs to be performed earlier in the workflow if we want to enrich ISO 19115 with the pre-reserved DOI. This deserves more thinking about ordering the actions (Investigate the question of workflow actions order #156)