[vector_graphics] Error handling enhancement

[minhhung2556]

Purpose

To fix these related issues below

• adjust vector_graphics errorBuilder (to trigger on BytesLoader errors) dnfield/vector_graphics#219

My related PRs

• Error handling enhancement dnfield/flutter_svg#1104
• Error handling enhancement dnfield/vector_graphics#258
• [flutter_svg] Error handling enhancement #8016
• This PR is preprocessor of [flutter_svg] Error handling enhancement #8062

Changes Made

• Enhance error handling in VectorGraphicWidget

Testing

• Already tested by example and unit test in flutter_svg

Impact

• This change should not affect other parts of the library.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or this PR is exempt from CHANGELOG changes.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[jonahwilliams]

Can you be more specific about what you mean by "enhance"?

This also needs a test

[minhhung2556]

Can you be more specific about what you mean by "enhance"?

This also needs a test

Hi, this PR changed the method _loadPicture to check some cases that could cause an error, such as: can not load the vector file, vector byte data is empty, and decodeVectorGraphics throws an exception.
I think this change can still be tested by the current unit test.
And This PR is preprocessor of #8062 and some changes in that PR I have new tests for it already.