Restructures into a R-package

[sk-sahu]

• Restructures individual R-Scripts into a R-package
• Adds CI/CD test for R-CMD check

[cgpu]

Thanks for this one @sk-sahu.

I have a few notes keeping in mind that we want to use best practices in package development to not have to migrate to another package structure in the future.

• For many reasons, including compatibility with other packages eg packagedown, having out of the box best practices in DESCRIPTION and depends etc, I would prefer we would use the usethis::create_package function for generating the skeleton of the package instead of manually adding the necessary files.
• for functions and variable names it would be better to use snake_case instead of camelCase
  this is suggested by many but here's a snippet from the Advanced R book.)
  This is taken care of from the linting action see below:
  

Variable and function names should be lowercase. Use an underscore () to separate words within a name. Generally, variable names should be nouns and function names should be verbs.

• we should take into account linting, can be from the lintr R package. For this I added an action but I have set it up only to give warnings and not fail the test. We should strive complying to best practices with a pinch of salt if sth is not possible to be changed.
• One more from Hadley Wickam's best practices, the name of the R package should not have a dash:

Unfortunately, this means you can’t use either hyphens or underscores, i.e., '-' or '', in your package name

Avoid using both upper and lower case letters: doing so makes the package name hard to type and even harder to remember. For example, I can never remember if it’s Rgtk2 or RGTK2 or RGtk2.

The repo therefore should be renamed to sth else eg. cloudosr or sth that respects naming conventions, open to more intuitive names.

[sk-sahu]

Closing this PR as another PR #3 is opened with implementing above suggestions.