3 Bar Chart expected output files and testing cases

[Jake-Bodin]

Description

Title is self sufficient, Jake Bodin's first pull request,
Fixes #[issue] ???

(In general, OED likes to have at least one issue associated with each pull request. Replace [issue] with the OED GitHub issue number. In the preview you will see an issue description if you hover over that number. You can create one yourself before doing this pull request. This is where details are normally given on what is being addressed. Note you should not use the word "Fixes" if it does not completely address the issue since the issue would automatically be closed on merging the pull request. In that case use "Partly Addresses #[issue].)

Type of change

(Check the ones that apply by placing an "x" instead of the space in the [ ] so it becomes [x])
???

• Note merging this changes the database configuration.
• This change requires a documentation update

Checklist

(Note what you have done by placing an "x" instead of the space in the [ ] so it becomes [x]. It is hoped you do all of them.)

• I have followed the OED pull request ideas
• I have removed text in ( ) from the issue request ???
• [ X] You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section.

Limitations

(Describe any issues that remain or work that should still be done.)

[Jake-Bodin]

The reason theirs so many calls is because I pushed to development when i meant to go to branch, it didn't matter but I wanted to fix and revert it, then I had some merge issues, not sure what they were, but everything should be good in the final merge to devolopment, that wont happen again.

[huss]

Thanks to @Jake-Bodin for doing this work and their first contribution to OED. The code is fine and works as expected. No changes are needed and it is ready to merge. Graduations on your first accepted work into OED.