Re-implement the remote action module approach

[thenets]

This repository (https://github.com/thenets/repo-automation/) is a GitHub Action but the current implementation requires the user to copy all the automation files instead.

Wrong design implementation

These are the workflows in the testing repo:

• https://github.com/dednets/repo-automation-test/blob/main/.github/workflows/repository-automation-trigger.yml
• https://github.com/dednets/repo-automation-test/blob/main/.github/workflows/repository-automation.yml

They are consuming files from the testing repo itself:

• https://github.com/dednets/repo-automation-test/tree/main/src

Expected result

• Nothing but the GitHub Action workflow files (https://github.com/dednets/repo-automation-test/blob/main/.github/workflows/repository-automation.yml and https://github.com/dednets/repo-automation-test/blob/main/.github/workflows/repository-automation-trigger.yml) should exist in the testing repo.
• The testing repo must consume the automation from this repo (https://github.com/thenets/repo-automation)

Example and documentation

Example of a well implemented GitHub Action workflow:

• https://github.com/actions/checkout

Here is the official documentation:

• https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows