This closes #2308, add RecalcOptions to scope File.Recalc to a sheet or range

[krystophny]

Description

Add a variadic RecalcOptions argument to (*File).Recalc so callers can narrow the sweep:

type RecalcOptions struct {
    Sheet string // limit recalc to a single worksheet
    Ref   string // limit recalc to an A1-style range (requires Sheet)
}

func (f *File) Recalc(opts ...RecalcOptions) error

An empty RecalcOptions (the zero value, also the default when no option is passed) preserves the whole-workbook behaviour introduced in the companion PR #2312. Setting Sheet narrows to one worksheet; setting Ref (which requires Sheet) narrows further to an A1 range. Invalid combinations produce a wrapped ErrParameterRequired or a clear diagnostic pointing at the offending field.

Related Issue

Closes #2308. Depends on #2311 (RecalcCell) and #2312 (whole-workbook Recalc). The branch is stacked on #2312 and will rebase cleanly on master once that PR merges.

Documentation

Reference-site entries for this PR ship in a companion docs PR: xuri/excelize-doc#31. That PR covers the English version; other language versions follow the project's usual rollout cadence.

Motivation and Context

Bulk whole-workbook recalc is overkill when a caller knows which part of the workbook changed. For large workbooks where a mutation touches one sheet, or a single row band, walking every formula on every sheet is wasted work. Scoping is additive to the API introduced by #2303 / #2312 and does not change the default behaviour.

How Has This Been Tested

$ go test -run 'TestRecalc' -timeout 60s -v . | tail -20
=== RUN   TestRecalcNonASCIISheetName
--- PASS: TestRecalcNonASCIISheetName (0.00s)
=== RUN   TestRecalcSheetScope
--- PASS: TestRecalcSheetScope (0.00s)
=== RUN   TestRecalcRefScope
--- PASS: TestRecalcRefScope (0.00s)
=== RUN   TestRecalcOptionRejects
--- PASS: TestRecalcOptionRejects (0.00s)
PASS
ok  	github.com/xuri/excelize/v2	0.016s

Full suite: go test -skip TestZip64 -timeout 10m . passes cleanly. gofmt -s -l . and go vet ./... are clean. ARM cross-builds (GOARM=5|6|7, arm64, android/arm64) all build.

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly (see companion docs PR Update en version docs for File.Recalc, RecalcCell, RecalcOptions, ErrCellNoFormula, and 3D range support xuri/excelize-doc#31).
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.