Use label.yml to determine required labels

[Tomvth]

Fixes

Fixes #884 by @AetherUnbound

Description

This PR implements both changes mentioned in the issue.

1. Instead of using a hardcoded list of labels explicitly defined in labels_pr.py, instead now the labels which have set is_required to True are parsed from the labels.yml data file.
2. The GET_ALL_CATEGORY_LABELS list is replaced and is also dynamically parsed from labels.yml, to do this a new apply_all_available boolean was added for each group.

Since labels.yml was encoded in utf-8, an optional argument to the load_data function was added to allow specifying the file encoding.

Testing Instructions

Run the labels_pr.py file, verify that the parsed list equates the original explicitly defined list.

Checklist

• My pull request has a descriptive title (not a vague title like
  Update index.md).
• My pull request targets the default branch of the repository (main) or
  a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible
  errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[AetherUnbound]

Thank you for the contribution! It looks like the linting checks might be failing, please try running just lint and committing the changes. I also have a few other suggestions for how to improve this approach.

[AetherUnbound]

Was this necessary for reading the file? Python should default to utf-8 when opening files if it's not set explicitly. Even if we needed to make this explicit here, we should just default to utf-8 anyway and avoid the need for the if encoding block below.

[Tomvth]

It seems that the encoding used by open() is platform-specific, although utf-8 seems to be the most prevalent. On my platform running open() on labels.yml results in UnicodeDecodeError: 'charmap' codec can't decode byte 0x8f in position 980: character maps to <undefined>. Specifying "utf-8" as encoding method fixes this.
I agree on making it the default and I removed the if statement, get_data() now defaults to utf-8.

[dhruvkb]

What platform are you using @Tomvth? Since these actions will be running inside GitHub Actions, the default encoding will be UTF-8.

[AetherUnbound]

This is excellent!! Thanks again for contributing 😄

[dhruvkb]

I like this very much, thanks @Tomvth!