Standardize artifact naming to align with project branding

[pacmano1]

To improve consistency and clarity across builds and distributions, update artifact (JAR) names to reflect Open Integration Engine branding rather than legacy naming. This will reduce downstream confusion in deployments, logging, and dependency management as the project continues to evolve independently.

Scope includes:

• Build outputs
• Distribution artifacts
• Any packaging references that surface artifact names externally

No functional changes intended.

[jonbartels]

What would be the general pattern? Replace com.mirth with org.oie or org.openintegrationengine? I prefer the shorter one.

What about MirthSomething classes? I think reducing it to Something would be better to avoid Smurf naming.

We should follow common naming convention practices. https://www.oracle.com/java/technologies/javase/codeconventions-namingconventions.html

The prefix of a unique package name is always written in all-lowercase ASCII letters and should be one of the top-level domain names, currently com, edu, gov, mil, net, org, or one of the English two-letter codes identifying countries as specified in ISO Standard 3166, 1981.
Subsequent components of the package name vary according to an organization's own internal naming conventions. Such conventions might specify that certain directory name components be division, department, project, machine, or login names.

How can this renaming be broken down into smaller chunks?

Can we or should we start introducing this pattern for NEW features?