New option to parse plugins.txt file

[sridamul]

Closes #77
Added new option to parse plugins.txt file

Testing done

Written unit tests

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[jonesbusy]

This is the repo name, not the plugin name.

I think we are wrongly using pluginName with -plugin suffix but in fact it's the repo name.

Perhaps we should clarifiy this in the tool before this PR.

Passing the plugin short name and getting the SCM url from the plugin center ? Or just ammending the -plugin to create the repo ? But I'm not sure it will work 100% of time

[gounthar]

Better safe than sorry, we should make it super clear in the documentation, the comments, and the code. 👍
Thanks for catching that early!

[jonesbusy]

Clarifiy usage of pluginName vs repo name

[sridamul]

I think I misunderstood in the previous conversation. I thought it would easier to look up the repo name instead of plugin name from the UC.

Passing the plugin short name and getting the SCM url from the plugin center ? Or just ammending the -plugin to create the repo ? But I'm not sure it will work 100% of time

I think it is better to get SCM link from uc

[sridamul]

Will create a PR to fetch SCM url from UC by passing the plugin short name (instead of passing the repo name in plugin option)