backgroundMetadataUpdater can log ErrNoTopicsToUpdateMetadata repetitively if client.conf.Metadata.Full is false

[dnwe]

Description

If the user has set client.conf.Metadata.Full to false then the refresh of metadata will log an error until the consumer has been assigned one or more topic partitions to refresh. It might also periodically log this if (e.g.,) metadata responses are throttled and don't contain any topics in the result

Versions

Sarama	Kafka	Go
v1.41.0	3.5.1	1.21.0

Configuration

client.conf.Metadata.Full = false

Logs

Client background metadata update: kafka: no specific topics to update metadata

Additional Context

N/A

[dnwe]

Looks like this had also previously been rightly reported as an issue with the admin client #2069

[github-actions]

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

[famarting]

do you think this change would be a good way to address this issue? #2830