Release v2.2.0

[#99] Add --build-history option to analyze (#109)

Includes establishing helper for BuildHistory structure and introducing BuildReportSummary.cs in UnityDataModels

[#55] Show type name in build_report_packed_asset_contents_view (#90)

Populate the types table from TypeIdRegistry when importing a BuildReport
so the packed asset contents view can display human-readable type names
instead of numeric class ids, even when the build output is not analyzed
alongside the report.

[#72] Add find-refs test coverage and fix its database/null-ref bugs (#…

…79)

* Introduce second UnityProject

Rename UnityFileSystemTestData and introduce a LeadingEdge project for testing Content Directory builds and other newer features that require Unity >=6.6.
Add AGENTS.md explaining the relationship between these projects and the referenced files checked in to TestCommon

* Dump command tested with core numeric field types and other serialization primitives

* [#72] Fix find-refs database open and null-ref crashes, add test coverage

find-refs had no automated tests and two bugs that broke it against any
current analyze database:

- Issue #72: the database was opened with a hand-written connection string
  using the legacy System.Data.SQLite "Version=3" keyword, which
  Microsoft.Data.Sqlite rejects. Build the connection string with
  SqliteConnectionStringBuilder instead (matching SQLiteWriter). Fixed the
  same broken string in ExpectedDataGenerator.

- A ScriptableObject is a MonoBehaviour whose m_GameObject PPtr is 0, so its
  game_object column is a non-null id matching no row; the game_object/script
  subqueries then return NULL and GetString threw. Null-check those reads.

Also add a --stdout option to find-refs (mutually exclusive with -o), mirroring
dump, and update command-find-refs.md.

Add FindRefsTests covering both bugs, name/type lookup and disambiguation,
object-id lookup, --find-all, missing objects, empty refs table, the
--stdout/-o validator, and direct refs-table queries. Tests run against the
LeadingEdge AssetBundle reference build.

[#77] Detect missing TypeTrees up front in analyze and dump (#78)

Analyzing AssetBundles whose SerializedFiles have no TypeTrees handed the
files to the native loader, which emitted misleading "Invalid serialized
file version" errors and could crash the process with an access violation
(0xC0000005)

Fix is to detect missing TypeTrees before the native open and skip such files cleanly,

Fix applies to both dump and analyze commands.
Fix applies to Player data and other build types in addition to AssetBundles.

Documentation improvements

Update the unity-content-format document to cross reference with the more powerful archive and serialized-file commands.

Added support for specifying an extracted type tree data file (#60)

* Added support for specifying an extracted type tree data file for dump and analyze commands
* updated docs & tests
* updated UnityFileSystem dlls to 6000.5.0a8 - this version has the API needed to load extracted type tree files.
* Bump version to 1.3.3
* Add a few additional AssetBundle test files

Fix issues in automated tests

A few failures had somehow slipped which were all bugs in the tests themselves (one because of a file move, two others were testing the wrong expected data)

Improve SerializedFile command and file type detection (#58)

Improve error reporting from serialized-file command
Use detection helpers to print more informative messages when command is run against the wrong file type.

Adding "header" subcommand for serialized file to print info from the serialized file header.

Detect and specific warning for YAML (text) format SerializedFiles

Example:
```
$ UnityDataTool.exe sf header .\AssetBundle.buildreport
Version              22
Format               Modern (64-bit)
File Size            12,280 bytes
Metadata Size        6,085 bytes
Data Offset          6,144
Endianness           Little Endian
```

Example:

```
$ UnityDataTool.exe sf objectlist .\Scene1.unity
Error: The file is a YAML-format SerializedFile, which is not supported.
File: C:\UnitySrc\unity\Modules\ContentBuild\Tests\ContentBuildTests\Assets\Scenes\Scene1.unity

UnityDataTool only supports binary-format SerializedFiles.
```

Add more small serializedfiles representing different legacy versions

Add test example of new extracted typetree format
New format with Unity 6.5 (v23 file with external typetrees in an archive)
Currently UnityDataTool cannot read the serialized file (except for printing the header)

v1.3.0 - MonoScript, BuildReport support in analyze, Doc improvement,…

… serialized-file command (#46)

* Update version to 1.3
* Add MonoScript handler to Analyze command
* Centralize docs in Documentation
* Analyze - Support BuildReport files (#45)
* New "serialized-file" command with docs and new test data (#47)