Add new tool: influx-si--data-manager v1.0.0

[llegregam]

FOR CONTRIBUTOR:

• - I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
• - License permits unrestricted use (educational + commercial)
• - This PR adds a new tool or tool collection
• - This PR updates an existing tool or tool collection
• - This PR does something else (explain below)

[bgruening]

• there is a strange Documents folder in this PR
  I'm a bit confused about the name "data manager". Data managers in Galaxy are very specific admin-only tools. This is not what you want to develop here, isn't it?

Maybe we can rename the tool and avoid the data-manager name?

[llegregam]

@bgruening

• there is a strange Documents folder in this PR

Apparently this was created by planemo during testing. It seems to have been a shortcut towards the galaxy folder I had configured for the tests. It has been removed

• I'm a bit confused about the name "data manager". Data managers in Galaxy are very specific admin-only tools. This is not what you want to develop here, isn't it?

Yes so long story short for a workflow I am building I used the term data manager for two specific tools that handle data interoperability within the workflow. This was before I noticed that the term would conflict with the Galaxy term. The problem is I already have one that is online under the name physiofit-data-manager, and I already have published the tool on pypi as well. So renaming would be a real hastle. I'm sorry for the confusion raised by this mistake...

*Maybe we can rename the tool and avoid the data-manager name?

See the answer above!

[llegregam]

@bgruening @lecorguille @yguitton
Could I please get a review or answers to my questions? :)

[bgruening]

This was before I noticed that the term would conflict with the Galaxy term. The problem is I already have one that is online under the name physiofit-data-manager, and I already have published the tool on pypi as well. So renaming would be a real hastle. I'm sorry for the confusion raised by this mistake...

You call, but I guess its better to change now, instead of adding more tools with this term. To be clear I'm only talking about the user facing name. The tool name etc. If the package/script is called like that is not important imho.