docs: add workflow to include labels after analyzing title of PR

About Regex Expression

You can test it here: https://regex101.com/

I am taking two examples, which you must read so that you can properly review the PR.

/\bfeat\b/: This regular expression matches the exact word "feat" with word boundaries (\b). It will match strings that contain the word "feat" as a whole word, but not if it's part of another word (e.g., "defeat" or "feature").
/feature/i: This regular expression matches the word "feature" (case-insensitive) anywhere within a string. It will match strings that contain "feature" in any combination of uppercase and lowercase letters (e.g., "Feature", "FEATURE", "feature").

I have checked issue forms and corresponding labels to properly use the config workflow.
I have not made this workflow for analyzing issues, so let me know.
I didn't found anything related to adding multiple labels at once, so I have used 1 label for 1 set.

There are two workflows that I found to implement this:

This is the only label goal: build that I have used since there was none. So, you can create them, or it will automatically be created during the analysis, but it will not be permanently stored in the labels of the repository.

- label: 'goal: build'
    regexs:
      - /build/i
    events: [pull_request]
    targets: [title]

Double check the issue forms, and the labels in the repository, because it will be a huge mess if the label is wrong.

Closes #473

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I've edited the SCRIPTS.md and link to my code.
[ ] I have created a helpful and easy to understand README.md
[ ] My documentation follows Template for README.md
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works.