Convert Boundary Object to use `long` instead of `int`

The latest versions of YamlDotNet use `long` instead of `int` for the index of yaml token objects, to be able to handle very large files. For now these are being cast to ints to keep the existing API surface, but the Boundary object should have its internal fields converted to long to be able to support those long files as well.