#16 CRUD get data by datatype name

[leoleader]

Changes

• Added getDataByDataTypeName CRUD Operation
• Added unit test for above
• Made Type ResponseFunction's data:JSON input required
  • Originally I opted for it to be optional but I think as design decision it's important for it to be required
• Updated unit tests accordingly with above

Checklist

It can be helpful to check the Checks and Files changed tabs.
Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.

• All commits are tagged with the ticket number
• No linting errors / newline at end of file warnings
• All code follows repository-configured prettier formatting
• No merge conflicts
• All checks passing
• Screenshots of UI changes (see Screenshots section)
• Remove any non-applicable sections of this template
• Assign the PR to yourself
• No package-lock.json changes (unless dependencies have changed)
• Request reviewers & ping on Slack
• PR is linked to the ticket (fill in the closes line below)

Closes # 16

[Peyton-McKee]

nice job, you can do it this way, idk if we should make the data be nonoptional though,

[Peyton-McKee]

see slack about type validating

[Peyton-McKee]

lets goooo