Feature #558 bar, box, histogram, revision_box

[georgemccabe]

Pull Request Testing

• Describe testing already performed for these changes:
  

Generated plots and reviewed differences from 555 branch

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

Explanation of diffs:

bar, box, histogram, revision_box - these are plots that have been switched to use matplotlib instead of plotly. The image sizes are different and the legend is properly displayed now. Please review these carefully and provide any feedback.

hovmoeller - differences are due to a bug that was introduced in feature_555 that was fixed in this PR. The non-plotly version of the Config object was accidentally being used, which caused the image size to change. The image generated by this branch actually looks more like the original from develop, although the "incorrect" one is bigger and has more details. The json file is also reverted back to the original, without the height and width specified. This will likely change again when we switch this plot to using matplotlib.

scatter - plot difference is fixing another bug where the plot contains the data/content of the performance_diagram plot instead of the scatter plot data/content. This was due to the plt object not being cleared out properly after each image is created.

performance_diagram - the size of the plot has changed, but the content is the same. This is because changed the base_plot.save_to_file function to call plt.savefig with the dpi set from the config and call plt.close('all') to clear the plot content. I changed the plots that call plt.savefig explicitly to call this function instead to be consistent. The new output uses the dpi value from the config (72) instead of the default (100).

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

• Do these changes include sufficient testing updates? [Yes]

• Will this PR result in changes to the test suite? [Yes]
  
  If yes, describe the new output and/or changes to the existing output:
  

See above

• Do these changes introduce new SonarQube findings? [No]
  
  If yes, please describe:

• Please complete this pull request review by 3/9/2026.
  

Pull Request Checklist

See the METplus Workflow for details.

• Add any new Python packages to the METplus Components Python Requirements table.
• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the version that will include these changes
  Select: Coordinated METplus-X.Y Support project for bugfix releases or METplotpy-X.Y.Z Development project for official releases
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.