Fix for error when running analyze on the buildreport.json on a build that hit a size > 2GB.
E.g. an individual AssetBundle file was more than 2GB
As precautionary measure change all "size" fields to long (although most should be very hard to reach that limit)

Fix for UNIQUE constraint failed SQL error
Avoid adding the same dependency more than once. This fixes errors discovered testing a large buildlayout.json

1. Fix Error Counting (Issue #48)
Problem: Files that failed to process were incorrectly counted as "successfully processed"

2. Improve Error Output Readability
Use relative paths in error messages
Single concise summary line per failure
Verbose mode shows detailed exception info

3. Fix BuildLayout Parser
Fixed AddressablesBuildLayoutParser.CanParse() to handle both minified and pretty-printed JSON
Previously only read the first line, which failed for pretty-printed JSON where the first line is just {
Now reads first 4KB and searches for the "BuildResultHash" field

4. Add Test Coverage

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)