feat: updating the api to better support a flexible input and adding …

[bvesterby]

…tests for round tripper testing

chore: rm doc files from v2 folder that aren't needed

fix: correct v2 module name

Description

Please describe what does this Pull Request fix or add?.

Information that is useful here:

• The What: What is your change doing?
• The Why: Why is the change necessary? What is the use case?
• Type of change
  Examples:
  • Bugfix
  • New feature
  • Code Quality Improvement
  • Dependency Upgrade
  • Documentation
• Breaking change: Yes or no? Backward compatible?
• Related to an issue: Does this fix or close an issue?

Examples

Let us know how users can use or test this functionality.

// Example code

Checklist

• Documentation
  • Code
  • Updated README or /docs/
• Unit or Integration tests added
  • Good Path
  • Error Path
• Commits follow conventions described here:
  • Conventional Commits 1.0.0
  • The seven rules of a great Git commit message
• Commits are squashed such that
  • There is 1 commit per isolated change
• I've not made extraneous commits/changes that are unrelated to my change.
• I have read the contributing guide