Jacoco-badge-generator

Fixed
* Suppressed Python's pycache on imports (fixes Issue 46).

Added
* Option to specify custom labels for the left side of the badges controlled
by the new inputs `coverage-label` and `branches-label`.

Changed
* Left-side text width and position calculated rather than hard-coded to
width of "coverage" and "branches".
* Changed Dockerfile to pull base image from GitHub Container Registry, assuming
within GitHub Actions likely faster to pull from GitHub rather than Docker Hub.
* Repository reorganized to move Python source code to a new src directory.

Added
* Option to generate a simple JSON summary report containing the coverage
and branches coverage values as double-precision floating-point values.
This may be useful as input to other tools. Additionally, if used in
combination with the existing `fail-on-coverage-decrease` and/or
`fail-on-branches-decrease` features, those checks will be more accurate.
This new feature is controlled by a pair of new inputs `generate-summary`
and `summary-filename`. This feature is disabled by default.

Fixed
* Visual improvements to right side of badges:
* Adjusted calculation of text lengths for right side of badges
for improved character spacing.
* Badge width now also adjusted by the right side text lengths.

Added
* Added an option to generate Shields.io JSON endpoints either in addition to,
or instead of, directly generating badges. For most users, the existing direct
generation of the badges is probably the preferred approach (e.g., probably
faster serving when loading README, and much simpler insertion of badge into
README). But for those who use one of Shields styles other than the default,
and who would like to be able to match the coverage badges to the style of
their project's other badges, then providing the ability to generate a
Shields JSON endpoint gives them the ability to do so. The new feature is
controlled by 4 new inputs: `generate-coverage-endpoint`, `generate-branches-endpoint`,
`coverage-endpoint-filename`, and `branches-endpoint-filename`. All of these
have default values and are optional. The current default behavior is retained,
so by default the JSON endpoints are not generated.

Added
* Customization of badge colors, using two new inputs (`colors` and
`intervals`). The defaults for the new inputs produce badges with
the existing color scheme.