Added support for new bun.lock format introduced in Bun v1.2 in BunPackageInstallerLifecycleHook

[r4hulp]

Closes #547

PR Checklist

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• PR doesn't include merge commits (always rebase on top of our main, if needed)
• New integration
  • Docs are written
  • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Contains NO breaking changes
• Every new API (including internal ones) has full XML docs
• Code follows all style conventions

Other information

Starting from Bun v1.2.0, the default lock file format changed from binary (bun.lockb) to text-based (bun.lock). This PR updates the BunPackageInstallerLifecycleHook to support both formats, ensuring compatibility with both older and newer versions of Bun.

Link to the blog - https://bun.sh/blog/bun-lock-text-lockfile

Changes

• Added check for both bun.lock and bun.lockb files
• Updated error messages to reflect support for both formats
• Added documentation comment explaining the version-specific changes

Before

var lockFilePath = Path.Combine(resource.WorkingDirectory, "bun.lockb");

if (!File.Exists(lockFilePath))
{
    throw new InvalidOperationException($"No bun.lockb file found in {resource.WorkingDirectory}");
}

After

// Bun v1.2 changed the default lockfile format to the text-based bun.lock
var lockbFilePath = Path.Combine(resource.WorkingDirectory, "bun.lockb");
var lockFilePath = Path.Combine(resource.WorkingDirectory, "bun.lock");

if (!(File.Exists(lockbFilePath) || File.Exists(lockFilePath)))
{
    throw new InvalidOperationException($"No bun.lock or bun.lockb file found in {resource.WorkingDirectory}");
}

Testing

• Tested with projects using Bun < v1.2.0 (bun.lockb)
• Tested with projects using Bun >= v1.2.0 (bun.lock)
• Verified error messages are clear when no lock file is present

Related Issues

Fixes #547

[r4hulp]

@dotnet-policy-service agree