Update vcpkg.json - lock flatbuffer version

[mc-nv]

Description

Locking version introduced in:

onnxruntime/onnxruntime/core/flatbuffers/schema/ort_training_checkpoint.fbs.h

Lines 11 to 13 in 03ea5dc

	static_assert(FLATBUFFERS_VERSION_MAJOR == 23 &&
	FLATBUFFERS_VERSION_MINOR == 5 &&
	FLATBUFFERS_VERSION_REVISION == 26,

Motivation and Context

Resolve issue for version >=1.20.
#22666

[mc-nv]

cc: @snnn

[snnn]

/azp run Big Models, Linux Android Emulator QNN CI Pipeline, Linux CPU CI Pipeline, Linux CPU Minimal Build E2E CI Pipeline, Linux GPU CI Pipeline

[snnn]

/azp run Linux GPU TensorRT CI Pipeline, Linux OpenVINO CI Pipeline, Linux QNN CI Pipeline, MacOS CI Pipeline, ONNX Runtime Web CI Pipeline, Windows ARM64 QNN CI Pipeline, Windows CPU CI Pipeline

[snnn]

/azp run Windows GPU CUDA CI Pipeline, Windows GPU DML CI Pipeline, Windows GPU Doc Gen CI Pipeline, Windows GPU TensorRT CI Pipeline, Windows x64 QNN CI Pipeline, onnxruntime-binary-size-checks-ci-pipeline

[azure-pipelines]

Azure Pipelines successfully started running 5 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 7 pipeline(s).

[snnn]

Thanks for the fix. All the build pipelines passed, but I don't think the change is necessary. ORT's source code can be built with the latest flatbuffer as long as the corresponding auto-generated C++ source files have been regenerated. When you see " static_assert failed: 'Non-compatible flatbuffers version included'" , it means you need to regenerate the source file with the correct flatc. We have a Github Action that builds ORT with the latest flatbuffer and it works well.
I will merge it now, and see if we can improve it later. I hope we can provide better flexibility on choosing the dependencies versions.