[bug]: OpenChannel with fundMax is restricted by maxChanSize

[feelancer21]

Pre-Submission Checklist

• I have searched the existing issues and believe this is a new bug.
• I am not asking a question about how to use lnd, but reporting a bug (otherwise open a discussion).

LND Version

v0.19.3

LND Configuration

tbd

Backend Version

v29.0.0

Backend Configuration

tbd

OS/Distribution

Debian

Bug Details & Steps to Reproduce

I openend a channel with --fund_max flag. The selected utxo was bigger than my maxchansize. Because of the description in lnd.conf I expected that maxchansize is irrelevant for an opening. But openning size was capped by maxchansize as well.

lnd/sample-lnd.conf

Lines 374 to 383 in 013f5c9

	; The largest channel size (in satoshis) that we should accept. Incoming
	; channels larger than this will be rejected. For non-Wumbo channels this
	; limit remains 16777215 satoshis by default as specified in BOLT-0002.
	; For wumbo channels this limit is 1,000,000,000 satoshis (10 BTC).
	; Set this config option explicitly to restrict your maximum channel size
	; to better align with your risk tolerance
	; Default:
	; maxchansize=<see explanations above>
	; Example:
	; maxchansize=10000000

lnd/rpcserver.go

Lines 2133 to 2141 in 013f5c9

	// If the FundMax flag is set, ensure that the acceptable minimum local
	// amount adheres to the amount to be pushed to the remote, and to
	// current rules, while also respecting the settings for the maximum
	// channel size.
	var minFundAmt, fundUpToMaxAmt btcutil.Amount
	if in.FundMax {
	// We assume the configured maximum channel size to be the upper
	// bound of our "maxed" out funding attempt.
	fundUpToMaxAmt = btcutil.Amount(r.cfg.MaxChanSize)

Expected Behavior

In my opinion, the restriction can be removed. However, if there is an important reason for it, at least the comment in the config should be adjusted.

Debug Information

No response

Environment

No response