Agreed @Tron the thing is this... if 'I' went and renamed the package file and many other things one does not normally to do in the quest for knowledge is it not entirely possible another person may do exactly the same and get stuck?
True, but if you follow those unwritten rules you should be able to fix any such issue in a jiffy.
I just do not want them to spend months searching for a fix like 'I' did is all 
Fair enough.
I am thinking of taking RC4 for a test drive so what should I do and what should I not to make each lazIDE co-exist peacefully?
For Lazarus things are quite simple, do:
1. Install in user space
2. Make sure each Lazarus installation uses its own configuration directory
Don't:
1. Install system wide or at the usual location that a package-manager or installer proposes by default.
2. Use a single configuration directory for all your Lazarus installations
The difficult part, if you consider it as such, is correctly installing and configuring the FPC compiler (or multiple versions that peacefully life next to each other) and which can be done using different solutions (one not necessarily smarter and/or better than the other though I do have my own personal preference).
FPCUpdeluxe for instance, solves the latter by providing each Lazarus installation with its own independent FPC compiler (which I personally consider a waste of space and defeats the intention of the compiler developers).
If you stick by those rules you should not encounter any issues whatsoever. At least I have not encountered any of the issues that are regularly mentioned on the forums simply by sticking to those simple (unwritten) rules. And fwiw, I have every FPC compiler that works on/for Linux installed (3.2.0 and up) (*), have a couple of dozen cross-compilers (it stacks up very quickly with different compiler versions) and a handful of Lazarus IDE's). Note that this does not include platform specific issues such as libc (linux) and xcode-tools (macos) for example.
(*) the same works for Windows and/or MacOS.