Add state to Geoscanner return

[Da5h1n]

PLEASE READ THE GUIDELINES BEFORE MAKING A CONTRIBUTION

• Please check if the PR fulfills these requirements

• The commit message are well described
• Docs have been added / updated (for features or maybe bugs which were noted). If not, please update the needed documentation here. Feel free to remove this check if you don't need it
• All changes have fully been tested

• What kind of change does this PR introduce? (Bug fix, feature, ...)
  Feature

• What is the current behavior? (You can also link to an open issue here)
  Geoscanners do not return Blockstate

• What is the new behavior (if this is a feature change)?
  Geoscanners can return Blockstate

• Does this PR introduce a breaking change? (What changes might users need to make in their scripts due to this PR?)
  No

• Other information:
  (my first time contributing on github, hope i done everything correctly)

[zyxkad]

Code generally looks good, just need some formatting & caching.

However, why is state needed in the result? What's the use example?

[github-actions]

Build Preview

You can find files attached to the below linked Workflow Run URL (Logs).

Name	Link
Commit	827244b
Logs	https://github.com/IntelligenceModding/AdvancedPeripherals/actions/runs/23661858193
Jar Files	AdvancedPeripherals PR 806
Expires At	2026-06-25T18:37:26Z

[SirEndii]

Check build log for checkstyle issues and resolve them

Also could you answer zyxkads question about the use case

[Da5h1n]

that should be fixed now
and im currently using this for a 3D dashboard im working on:

probably not the best use case but it can probably help with waterlogged blocks and mining turtles

[Da5h1n]

ive tested it both on turtles and as a peripheral and it works fine

[zyxkad]

Since it is a new feature, I'll merge it into 0.8.