Add CI testing for name clashes

Adding a CI job to look for naming clashes. Context: #279 (closed)

The purpose of this script is not to reimplement the exact package specification but rather to detect potential issues and package clashes based on whether or not the corresponding package registries perform package lookups in a case-sensitive or case-insensitive manner.

At the moment the detection is pretty basic as it looks for matching clashes so that we should be able to catch obvious clashes. However, in the future we may want to add more checks to catch typos or package slug mismatches by using Levenshtein or other metrics.

Package Manager	Case-Sensitive	Documentation
npm	Yes	Package name rules
Conan	Assuming Yes because it is filesystem-based	Conanfile attributes - name
Maven	Yes	Guide to naming conventions on groupId, artifactId, and version
Packagist	Yes	Submission Checklist - Naming Your Package
Go Modules	No	Package names
PyPI	No	PEP 503 - Simple Repository API
RubyGems	No	Name your gem
NuGet	No	Package ID prefix reservation