Draft: Support camelcase jsonl names

[pnadolny13]

Closes: #29

Problem

Default to case insensitive for jsonl records.

Types of changes

What types of changes does your code introduce to PipelineWise?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• Description above provides context of the change
• I have added tests that prove my fix is effective or that my feature works
• Unit tests for changes (not needed for documentation changes)
• CI checks pass with my changes
• Bumping version in setup.py is an individual PR and not mixed with feature or bugfix PRs
• Commit message/PR title starts with [AP-NNNN] (if applicable. AP-NNNN = JIRA ID)
• Branch name starts with AP-NNN (if applicable. AP-NNN = JIRA ID)
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions

[aaronsteers]

@pnadolny13 - Thanks for submitting! I've approved. Feel free to merge - if you have permissions - or just ping me again to merge when ready if permissions are not there.

[pnadolny13]

@pnadolny13 - Thanks for submitting! I've approved. Feel free to merge - if you have permissions - or just ping me again to merge when ready if permissions are not there.

@aaronsteers awesome, thanks! It looks like I don't have merge permission. Can you merge it for me whenever you have a minute?