Address panic observed while operating with file callbacks

[abhinavdangeti]

• Separating vector tests out of the original file, to run unrelated tests in non-vectors mode.
• Update github workflows for newer versions of GO.
• Panic stack trace ..

--- FAIL: TestFileCallbacks (0.01s)
panic: runtime error: slice bounds out of range [18446744073709551611:3] [recovered, repanicked]

goroutine 35 [running]:
testing.tRunner.func1.2({0x10041d8c0, 0x14000018780})
	/opt/homebrew/Cellar/go/1.25.6/libexec/src/testing/testing.go:1872 +0x190
testing.tRunner.func1()
	/opt/homebrew/Cellar/go/1.25.6/libexec/src/testing/testing.go:1875 +0x31c
panic({0x10041d8c0?, 0x14000018780?})
	/opt/homebrew/Cellar/go/1.25.6/libexec/src/runtime/panic.go:783 +0x120
github.com/blevesearch/zapx/v17.(*SegmentBase).loadFieldDocValueReader(0x60?, {0x140002fe763?, 0x5?}, 0x5, 0x140000e5ba8?)
	/Users/abhinav.dangeti/Documents/go/src/github.com/blevesearch/zapx/docvalues.go:123 +0x3b0
github.com/blevesearch/zapx/v17.(*SegmentBase).loadDvReaders(0x14000000140)
	/Users/abhinav.dangeti/Documents/go/src/github.com/blevesearch/zapx/segment.go:835 +0x2d0
github.com/blevesearch/zapx/v17.(*ZapPlugin).open(0x1400015e100?, {0x14000404a40, 0x3b}, 0x0)
	/Users/abhinav.dangeti/Documents/go/src/github.com/blevesearch/zapx/segment.go:94 +0x26c
github.com/blevesearch/zapx/v17.(*ZapPlugin).Open(...)
	/Users/abhinav.dangeti/Documents/go/src/github.com/blevesearch/zapx/segment.go:49
github.com/blevesearch/zapx/v17.TestOpen(0x14000161a40)
	/Users/abhinav.dangeti/Documents/go/src/github.com/blevesearch/zapx/segment_test.go:40 +0xac
github.com/blevesearch/zapx/v17.TestFileCallbacks(0x14000161a40)
	/Users/abhinav.dangeti/Documents/go/src/github.com/blevesearch/zapx/file_callbacks_test.go:133 +0x28
testing.tRunner(0x14000161a40, 0x100434ea8)
	/opt/homebrew/Cellar/go/1.25.6/libexec/src/testing/testing.go:1934 +0xc8
created by testing.(*T).Run in goroutine 1
	/opt/homebrew/Cellar/go/1.25.6/libexec/src/testing/testing.go:1997 +0x364

[CascadingRadium]

Looks like this is a real bug, we did not seem to catch this before as the workflows did not run the file callbacks tests - due to it being hidden under the vector go tag.

[CascadingRadium]

LGTM, i think @Likith101 can address the panic in a separate patch.

No, let's address the failure in this PR - alongside the tests that will now run in CV.

[Thejas-bhat]

looks good, but maybe you can throw in an in-line comment which summarizes the fact that rewriteSegmentBases() persists the segment into the writer with footer, so we can early exit over there?

[abhinavdangeti]

Nice one @Likith101 👍🏼 .
@Thejas-bhat good call on the comment - I've added one.

[abhinavdangeti]

v17.1.1