moves validator code into prompting package

[p-ferreira]

This PR moves the validator init code into the prompting package. This facilitates the code to be accessed within the prompting package scope, making in it easy to integrate with pip install @git/prompting (useful for applications built on top of prompting code).

[bkb2135]

Does this mean that miners will have to build environments to support the entire validator code? I know that currently they have to anyway, but will this make decoupling the requirements impossible in the future?

[p-ferreira]

Does this mean that miners will have to build environments to support the entire validator code? I know that currently they have to anyway, but will this make decoupling the requirements impossible in the future?

This change means that all the code from the validator class is packaged alongside all the remaining code of the validators, which should be ok considering that validators shouldn’t have dependencies out of the requirements scope.

Now talking about the miners, I do believe that custom miners get accompanied with custom requirements, where they could reference the prompting repo itself as one requirement of their suite, so it's still decoupled in the same fashion we are decoupled from bittensor.