Replace "This is fatal error" in several exception messages with "This is a fatal error"
Various fixes for overloading operator conflict detection

If a role consumes another role, the consuming role's overloaded operators
just win, rather than being a conflict. Fallback setting conflicts are still a
conflict, however.

If there are operator conflicts during role summation we check the method
bodies and only make it a conflict if the bodies are different. This handles
the case where two roles got their overloading from the same source (another
role).
Merge pull request #79 from moose/topic/smarter-overloading-conflict-detection

Fix overloading conflict detection
remove extra cruft
changelog for Moose-2.1301-TRIAL
Make overload fallback conflicts from role-consumes-role work like other conflicts - consumer silently wins

Also fixed the docs on overloading conflicts to match reality.
Remove package {} syntax from tests
Merge pull request #80 from moose/topic/more-overloading-conflict-tweaks

More overloading conflict fixes
rename these test packages to avoid using B
bump version to 2.1302
changelog for Moose-2.1302-TRIAL
changelog for Moose-2.1302-TRIAL
until [Authority] is fixed, use our own implementation

Avoid the hundreds of annoying "consider adding a "# AUTHORITY" comment" warnings
add comment to my ugly hack
add some test labels
TODO tests for RT#98488 (meta_name not working as advertised)
bump required version of [Conflicts], to bring back the -also section
oops, this really should be a TODO test for now.
bump the [Conflicts] version, to get a .pm immune to podweaving
set_prototype was added in Scalar::Util 1.11

We require a version higher than that in metadata already, but it can't hurt
to make sure.