Update documentation prior to RC for CRAN

[villegar]

• Updated documentation to resolve NOTES from the tools::checkRd function
• Updated README file to align with dsBase's README
• Updated DESCRIPTION file to wrap occurrences of DataSHIELD with single quotes
• Added CITATION file

[StuartWheater]

Do we need to also run devtools::build_site?

[StuartWheater]

Are the 'git actions' test failing significant?
Does a line container ^.github$ added to the .Rbuildignore file?

[StuartWheater]

Does "spelling" need to be added to DESCRIPTION's "Suggests" section

[StuartWheater]

• Does a line containing ^.github$ need to be added to the .Rbuildignore file?
• Are the 'git actions' test failing significant?
• Does "spelling" need to be added to DESCRIPTION's "Suggests" section

[villegar]

Are the 'git actions' test failing significant? Does a line container ^.github$ added to the .Rbuildignore file?

The issue with Windows has been solved, but with other runners, like Ubuntu, the issue seems to be that dsBase is not found by the installation:

Error: Error: dsBase package is required in the local R installation for the execution of the tests.

I have updated the .Rbuildignore to ignore the .github directory.

[StuartWheater]

Is "the issue seems to be that dsBase is not found by the installation" going to affect a users experience?

[villegar]

Is "the issue seems to be that dsBase is not found by the installation" going to affect a users experience?

The introduction of the GitHub Action workflows should not affect the users' experience, this is mostly to automate the checks we do. So, I'm thinking I have probably missed something obvious, like configuring a server in the yaml file. Perhaps we drop the GitHub standard test workflow, so we can get an RC.

[StuartWheater]

Can we disable/skip those tests?