A description what has happened here and why these problems occur (even with multiple different addons):
Libraries are reusable code. Some addons include them in subfolders (which is okay if they also include the Lib*.txt file which the game's addon manager recognizes and loads properly then).
Others just add the dependency to their own addon's txt files and thus the game's addon manager wil look for ANY of th Lib*.txt files in ANY of your live/AddOns subfolders (up to sublevel 3!).
If any version is found it will load that version and use it.
If a newer version is found (all handled by the the Lib*.txt files, and their tag ## AddOnVersion: <number>) it will ONLY load this version then.
This assures that only the newest version of a lib is loaded.

But some older addons, but also (sad but true) even commonly used and recently updated addons, do not handle it like this.
They will put the libs in the subfolders of the addon WITHOUT the Lib*.txt file. So there are only the Lib*.lua files.
And in the addon's txt file (e.g. LazyWritCreator.txt), which the game always loads and checks what other files to include for the addon to be able to work, they call the lib's lua files "hardcoded" with lines like /libs/Lib*.lua
This will make the lua code of the libs, no matter which verison was included (could be very old, or could be the most actual one), to be executed.
Even if the ingame addon manager has already loaded a newer version (via the Lib*.txt file properly) before.
So the old code will/might overwrite the newer one breaking several addons that way.
Even if the devs include a Lib'.lua file with the most current version today: In a few days there might be a patch to that Lib and then the included version is "old again".
if they do not include the Lib*.txt file as well, which will make the ingame addon manager to check and not load the old version then, as it will find a newer version elsewhere (e.g. in live/AddOns/Lib*), the old code will destroy newer ones

The easiest fix is to remove the "hardcoded" calls to the libs. Either by manipulating the txt files of the addons where these hardcoded lines are in.
Or by deleing the Lib*.lua files in the subfolder "libs" of addons.

But attention:
There might be libraries in the subfolders of addons which have NEVER been released to the public (cannot be found at www.esoui.com and thus not at Minion)! So always check if the library in the subfolder is on esoui or not. If not: Keep the files of that lib as it might be missign elese and break your addon.
But if it is given at esoui: Install that library from esoui manually/via Minion to your live/AddOns folder and keep it updated there. Remove the same library from any subfolder of other addons!

Benefit:
The lib will be only called from live/AddOns/Lib* then. Only 1 place to check in case of errors and only 1 place to update (even works via Minion then).

Downside:
Some addons which had the hardcoded lines in their txt files did not specify the "## DependsOn: Lib*" or "## OptionalDependsOn: Lib*" in their addon's txt file. They did not need to as the hardcoded lines were always loaded.
But these (Optional)DependsOn says the addon that the library will be needed to be called BEFORE the addon is loaded in order to provide data to the addon e.g.

So either add the library name to the DependsOn lines of the addons where you have deleted the subfolder "libs" entries, like e.g.

## DependsOn: LibAddonMenu-2.0 LibCustomMenu LibSets

-> The name to add is the name of the folder of txt file of the library, e.g. LibAddonMenu-2.0.txt, or LibCustomMenu.txt, or LibSets.txt

Or try if everything works okay and leave it the way it is.