No error stack when plugin module cannot be found

[JoshuaKGoldberg]

Spinning off of #1043: if a plugin name cannot be resolved, the thrown error doesn't include an explanation of why or which paths were attempted. I think it might be useful to include that information. Do you think logging the caught errors in lib/plugin/factory's load sounds reasonable?

release-it/lib/plugin/factory.js

Line 24 in c1c0f99

const load = async pluginName => {