file: load from file should allow configure maxBytes

[makasim]

It is needed to implement same behavior as LoadFromFileOrNew does. It respects given maxBytes and pass it to load so this check

fastcache/file.go

Lines 133 to 139 in e439f07

	if maxBytes > 0 {
	maxBucketBytes := uint64((maxBytes + bucketsCount - 1) / bucketsCount)
	expectedBucketChunks := (maxBucketBytes + chunkSize - 1) / chunkSize
	if maxBucketChunks != expectedBucketChunks {
	return nil, fmt.Errorf("cache file %s contains maxBytes=%d; want %d", filePath, maxBytes, expectedBucketChunks*chunkSize*bucketsCount)
	}
	}

works.

Related to https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8952/files

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.96%. Comparing base (e439f07) to head (4905d51).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #86   +/-   ##
=======================================
  Coverage   76.96%   76.96%           
=======================================
  Files           4        4           
  Lines         547      547           
=======================================
  Hits          421      421           
  Misses         71       71           
  Partials       55       55           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[valyala]

@makasim , @zekker6 .

This pull request breaks users' code, since it changes the signature of the public function - LoadFromFile() - from LoadFromFile(filePath string) to LoadFromFile(filePath string, maxBytes int). This is a big no-go for public Go packages - see https://go.dev/doc/modules/release-workflow#breaking . Please return back the signature of the LoadFromFile() function to the previous one, add a new public function, which accepts maxBytes argument and make a new release, which fixes the breaking change.

Note that this rule must be applied to all our public packages, which have v1.* release (e.g. stable release).

[makasim]

@valyala Apologies for this, it's entirely my fault. I'll get it fixed right away.

[makasim]

reverted in #88