arrow

GH-33977: [Dev] PR Workflow automation bot (#34161)

### Rationale for this change

As discussed on the [mailing list](https://lists.apache.org/thread/1rhsd8ovy4bfr8hcdohn0vh65frw0ggk) is quite difficult to understand the current state of a PR whether it requires further review, it has gone stale or new changes have been added. This allows us to have a set of labels based on the state of the PR.

```mermaid
flowchart TD
    A([New PR]):::creator
    A -- by non-committer --> B[Awaiting review]:::anyone
    A -- by committer --> C[Awaiting commiter review]:::committer
    B & C -- new review by\nanother non-committer --> C
    C & B & E  -- new committer review\nrequests changes --> D[Awaiting changes]:::creator
    D -- changes by creator --> E[Awaiting change review]:::committer
    C & E & B -- new committer review\napproves ---> F[Awaiting merge]:::committer
classDef creator stroke:#CC0;
classDef anyone stroke:#00C;
classDef committer stroke:#0C0;
classDef triager stroke:#C0C;
linkStyle 0,1,7 stroke:#CC0,color:auto;
linkStyle 2,3 stroke:#00C,color:auto;
linkStyle 4,5,6,8,9,10 stroke:#0C0,color:auto;
```
### What changes are included in this PR?

New workflow to trigger archery bot on the required actions. New PR Workflow bot implementation on archery that manages the GitHub events and state.
New fixtures and tests.

### Are these changes tested?

There are unit tests and has been tested on my fork. Some transition examples on this PR:
https://github.com/raulcd/arrow/pull/74

* Closes: #33977

Authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>