Improve usage example and tests

[hgraceb]

• Improve tests.
• Improve usage example for Dio.download.
• Remove unused code.
• Fix typo in example/lib/download_with_trunks.
• Replace the broken resource: http://download.dcloud.net.cn/HBuilder.9.0.2.macosx_64.dmg.
• Disable the compression to assure the value of total argument of onReceiveProgress is not -1 in example/lib/download.

New Pull Request Checklist

• I have read the Documentation
• I have searched for a similar pull request in the project and found none
• I have updated this branch with the latest main branch to avoid conflicts (via merge from master or rebase)
• I have added the required tests to prove the fix/feature I'm adding
• I have updated the documentation (if necessary)
• I have run the tests without failures
• I have updated the CHANGELOG.md in the corresponding package

Additional context and info (if any)

There was no warning previously due to the default dynamic parameter type.

[ueman]

Suggested change

	/// onReceiveProgress: (received, total) {
	/// if (total != -1) {
	/// print((received / total * 100).toStringAsFixed(0) + '%');
	/// print('${(received / total * 100).toStringAsFixed(0)}%');
	/// }
	/// },
	/// onReceiveProgress: (received, total) {
	/// if(total < 1) return;
	/// final percentage = (received / total * 100).toStringAsFixed(0)
	/// print('$percentage%');
	/// },

[ueman]

Suggested change

	if (total != -1) {
	print((received / total * 100).toStringAsFixed(0) + '%');
	print('${(received / total * 100).toStringAsFixed(0)}%');
	}
	if (total < 1) return;
	final percentage = (received / total * 100).toStringAsFixed(0)
	print('$percentage%');

[hgraceb]

• I replaced 1 with 0 because 0 is the actual boundary value.
• I merged the definition and the print statement together.

-  if (total < 1) return;
-  final percentage = (received / total * 100).toStringAsFixed(0)
-  print('$percentage%');
+  if (total <= 0) return;
+  print('percentage: ${(received / total * 100).toStringAsFixed(0)}%');

[ueman]

I replaced 1 with 0 because 0 is the actual boundary value.

That's fine for me.

I merged the definition and the print statement together.

I believe that's harder to read, but since no one else complained, it seems like that's a me problem :D

[ueman]

Good catch!