feat: repurpose targeted jobs

[narbs91]

Summary

This pull request makes the following changes:

• Updates the allow list check to instead check if the RP is in the test list. thus requiring that they prove their capability to run a job on the network.
• Creates a new path for RPs on the test list to be able to submit resource offers but these will be saved with a new job state called PendingTesting. Additionally, the RP will receive a message telling them they are up for testing before being able to have their resource offer available for regular matching on the network
• Todo: Updates the targeted job functionally in the solver loop to only work with RPs who are part of the test list and have a resource offer with state PendingTesting
• TODO: See if there is any changes that need to be done to the GetResourceOffers method in the memory store

Explain the motivation for making these changes. Does this pull request implement a feature or fix a bug? Is it a docs change or a typo fix?

Task/Issue reference

Closes: add_link_here

Test plan

Please describe how reviewers can test the changes in this pull request. If the test plan is challenging to explain in text alone, a short video demonstration may be included.

To test this PR, one will need to run the admin service locally, add their RP (0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65) to the test list, then run the lilypad stack locally. Once the RP attempts to submit an resource offer, it should be saved by the solver with the PendingTesting and be available to run a job with only the target flag (and not be available to be matched in the regular way).

On the flip side, you'll want to test that the RP cannot use the target flag when they are on the allow list (and thus not subject for testing)

Details (optional)

Add any additional details that will help to review this pull request.

Related issues or PRs (optional)

Add any related issues or PRs.