Contributing: 'junior job' renamed to 'good first issue'

(cherry picked from commit c6f53ca65c03c49d57ebe5b716a475359a58c84e)

community/contributing/bug_triage_guidelines.rst

@@ -70,8 +70,8 @@ The following labels are currently defined in the Godot repository:
    `godot-proposals <https://github.com/godotengine/godot-proposals>`__ instead.
 -  *For PR meeting*: the issue needs to be discussed in a pull request meeting.
    These meetings are public and are held on the `Godot Contributors Chat <https://chat.godotengine.org/>`_.
--  *Junior job*: the issue is *assumed* to be an easy one to fix, which makes
-   it a great fit for junior contributors who need to become familiar with
+-  *Good first issue*: the issue is *assumed* to be an easy one to fix, which makes
+   it a great fit for new contributors who need to become familiar with
    the code base.
 -  *High priority:* the issue is particularly important as it can
    prevent people from releasing their projects or cause data loss.

community/contributing/ways_to_contribute.rst

@@ -84,8 +84,9 @@ To ensure good collaboration and overall quality, the Godot developers
 enforce some rules for code contributions, for example regarding the style to
 use in the C++ code (indentation, brackets, etc.) or the Git and PR workflow.
 
-A good place to start is by searching for issues tagged as `junior jobs <https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3A%22junior+job%22>`_
-(or `Hacktoberfest <https://github.com/godotengine/godot/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3AHacktoberfest+>`_ during October) on GitHub.
+A good place to start is by searching for issues tagged as
+`good first issue <https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22>`_
+on GitHub.
 
 .. seealso:: Technical details about the PR workflow are outlined in a
              specific section, :ref:`doc_pr_workflow`.