chore: Cran submission

[albersonmiranda]

What type of PR is this? (check all applicable)

• [x] Refactor
• [ ] Feature
• [x] Bug Fix
• [ ] Optimization
• [x] Documentation Update
• [ ] Tests

Description

Several issues were addressed in order to get the package ready for CRAN submission:

• Refactor $set_max_threads() method for better parallelism control and error handling.
• Complete rewrite on documentation. CRAN revisor pointed that out documented unexported functions, so added @noRd to Rust files (*.rs). that documentation were moved to respective method in R6.R.
• Added settings to enable offline build and include Rust dependencies.
• Fixed typo on value-added term everywhere.

Related Tickets & Documents

• Closes #13

Added/updated tests?

Goal is code coverage percentage at 80% and above.

• [x] Yes
• [ ] No, and this is why: please replace this line with details on why tests have not been included
• [ ] I need help with writing tests

Pre-merge checklist

• [x] PR title follows semantic commit guidelines (e.g., fix:, feat:, refactor:, test:, docs:)

Release checklist

• [x] Bump version (both Rust & R packages, accordingly)
• [x] Update NEWS.md

If dev release

• [ ] Precompiled Linux binaries
• [ ] Precompiled Windows binaries devtools::check_win_devel()
• [ ] Precompiled macOS binaries devtools::check_mac_release()
• [ ] Update tag:
  • git tag -m "update tag to new commit" -f -a TAG COMMIT_SHA
  • git push -f origin refs/tags/TAG

[albersonmiranda]

Submitted, waiting for approval! 🎉

[albersonmiranda]

Aproved! 🎉