Use consistent branch names in README.md

[liontiger23]

Previously examples were inconsistent between workflow examples and points bar code examples

[markpatterson27]

@liontiger23 Thank you for the PR.

The branch name is configurable so that users can choose their preferred naming convention. Do you think that having different branch names in the examples is confusing for new users trying to setup points bar in their own repo?

I wonder if a better solution would be adding guidence on using a different branch name (i.e. matching workflow ignore, checkout and blob path)?

Your opinions on this would be valuable.

[liontiger23]

This was by far the biggest point of confusion for me.

Both previous code snippets were copy-pasteable, so everything would work "out-of-the-box". So I assumed the same for this <img> example, but it failed, and I had to go dig into URL to find out why.

The changes below were just to ensure that the same snippets will work for reusable workflow as well.

[liontiger23]

I wonder if a better solution would be adding guidence on using a different branch name (i.e. matching workflow ignore, checkout and blob path)?

To highlight the ability to change the branch, and make it visible to new user, it would probably better to use status as example branch, so that it stands out (since the path to .svg also contains badges --- /blob/badges/.github/badges/points-bar.svg).
I would think after that, a note about replacing status branch with a different one will be enough.