Add CC: Tweaked peripheral for ghost programmed circuit

[blockninja124]

What

This PR adds a CC: Tweaked generic peripheral with getProgrammedCircuit() -> nil|0-32 and setProgrammedCircuit(nil|0-32).

This properly finishes the implementation for CC:T described here #806

Implementation Details

The generic peripheral applies to all machines / machine traits that implement IHasCircuitSlot. To do this, I have added a capability CAPABILITY_CIRCUIT_SLOT which is added in MetaMachineBlockEntity like all the other GregTech CC compat capabilities.

[TarLaboratories]

LGTM except one comment

[TarLaboratories]

why add a commented out line?

[blockninja124]

So that it can be uncommented easily for testing in runtime, I saw some of the other dependencies doing that aswell. I can remove the line if you want.

[screret]

Is it not already a part of the extraLocalRuntime group?

[blockninja124]

If it is, I couldn't find it?

[TarLaboratories]

Also please run the spotlessApply gradle task for formatting

[blockninja124]

spotlessApply didn't seem to change any files to commit?

[blockninja124]

I have moved the commented out CC dependency to where the other modExtraLocalRuntime dependencies are. (I have also uncommented it).

I managed to run ./gradlew spotlessCheck --warning-mode all, then ./gradlew spotlessApply, and committed the changes it performed.

[Ghostipedia]

This should have absolutely not have been merged.
There is under no circumstances meant to be ways in our API to change circuit #'s and this should strictly be either add-on territory or mod-pack territory. This is an extreme balance implication that should have been discussed prior.

This PR will be forcibly reverted and this is a friendly reminder to please discuss heavy balance / cross mod integration on discord before submitting PR's.

[blockninja124]

I was told when I asked in the github issue #806 that if I made a PR for this, it would be considered for merging. I was not informed that it would go against balancing, which is why I submitted it.

I think its unfortunate this is considered unbalanced, considering most modpacks I have played gate computers at about HV, and to make use of this circuit api you would need to write a decently clever script to manage items in and out of your machine. It could even be considered an improvement for servers, since the alternative is building more machines, one for each programmed circuit. (Which, admittedly, is probably more expensive, but definitely not out of the question for some players).

[blockninja124]

Additionally, with using a computer and one machine to automate many recipes, you are trading off the speed at which you can process multiple recipes. Sure, it may have been cheaper to setup, but you will end up with a backlog of items if you need to queue two different circuit recipes at once. Meaning that a dedicated machine for each recipe is the ideal solution to aim for anyway, and this api is simply something to engineer with in the meantime.