Improve how internal errors are propagated to users and when debugging issues

[abn]

As things stand today, the internal errors that happen when issues like #2737 #2734 are encountered are lost to the logger.

poetry/poetry/inspection/info.py

Lines 153 to 160 in cae154c

	except ValueError:
	# Likely unable to parse constraint so we skip it
	self._log(
	"Invalid constraint ({}) found in {}-{} dependencies, "
	"skipping".format(req, package.name, package.version),
	level="debug",
	)
	continue

This needs to be improved such that we use an application level logger with an option to generate debug logs if/when required without interfering with the CLI UX.

[ewjoachim]

(perfect 👍 thank you)

[abn]

@sdispater Is there some processing missing here?

PyPI: No release information found for django-1.1.2, skipping
PyPI: 1 packages found for django >=3.0.8,<4.0.0
<debug>PackageInfo:</debug> Invalid constraint (asgiref (~=3.2)) found in django-3.0.8 dependencies, skipping
   1: fact: django (3.0.8) depends on pytz (*)
   1: fact: django (3.0.8) depends on sqlparse (>=0.2.2)

I was expecting <debug> to be rendered correctly.

[sdispater]

@abn It's rendered correctly on my end:

[abn]

@abn It's rendered correctly on my end:

Strange. Not sure why that single debug won't render as expected on mine. Will debug later then.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.