Expanding Test Data For Local Development

## User Story

In order to provide developers with more data to test against, developers want to add more test data for manual testing.

## Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development#Behavioral_specifications).]

- [ ] GIVEN the `testdata` command \
WHEN it is ran \
THEN it generates at least 3 Organizations, 2 harvest sources each, with 2 datasets for each source

## Background

Currently devs have 1 test organization along with 1 harvest source, and 50+ datasets. However the datasets don't provide enough variation to test out more complex searches. This leaves developers in need of taking over development to have a greater set of data. Sometimes this process means having to also resolve mrge conflicts with the current develop branch to not interfere with other devs work.

However if devs were able to have more variation locally it could provide a faster way to manually test new features and expose any bugs that may not be noticed on development.

## Security Considerations ([required](https://nvd.nist.gov/800-53/Rev4/control/CM-4))

[comment]: # "Our SSP says 'The Data.gov team ensures security implications are considered as part of the agile requirements refinement process by including a section in the issue template used as a basis for new work.' so please don't remove this section without care."
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

## Sketch

[Notes or a checklist reflecting our understanding of the selected approach]