How to completely sterilize a project from anything related to addressables?

A few weeks ago I encountered an issue and reported it on this forum and I was told to try solving it by adding the Localization package. I had no use for it though but I went on with the suggestion. When observing that it wasn’t doing much change, I wondered if I should keep it or not, tempted to see if I could exploit it for a later use. But I decided to remove it.
Then I got an error (can’t remember which one) because of said removal, so I brought it back. And then when running the app in Editor or when building it, I was told that some things were missing, so I went creating a locale, I created a localization settings file, etc.
Totally unnecessary stuff as far as I was concerned but Unity was asking me to at least do all of this.
Lately, I hit another issue which for some reason required of me to create at least one “locale” and fiddle with addressables, which I never used. Frankly I find the menus needlessly confusing.

I had enough of this so I decided to delete the Adressables folder in Assets (its name is longer) and remove the Localization package again, then delete the Library folder and relaunch Unity. I wanted to revert to a state in my project that simply existed before, as I still have no need for any of this.
But after getting back into Unity, switching back to the iOS environment, then pressing Run, I got these five errors:

I have not added code or components that I know of that use Localization or any of these addressables.
I just want to clean the project and get rid of these pesky errors. I have no idea what is requiring any of this and throwing these errors.
What should I do?

Probably revert your project prior to this point with your version control software.

That’s the dirty solution that doesn’t explain what is going on. Unfortunately, while the addressable related issue is rather fresh, I’ve had the Localization package for weeks in the project, staying dormant except for that one non-pressing issue.
What puzzles me is why Unity is behaving the way it does regarding tools I didn’t even integrate in the project. Integrate here meaning I didn’t create any scene, script, asset or add any component that depended on locales or addressables. The project is fairly simple.

Don’t see how that’s the dirty solution. This is exactly what version control is for.

And plenty of packages can be included in projects implicitly as dependencies of other packages. Localization depends on Addressables, so adding the former also adds the latter.

It looks like Addressables is still in your project for whatever reason. Hell it looks like Localisation is still present. So either remove them via the package manager if either are still present, or edit your manifest.json file to exclude them.

Newer Unity versions show implicitly added packages in the package manager, but in older versions you can still see all the packages that have been added (implicitly or otherwise) by just expanding the packages folder:
9780222--1402431--upload_2024-4-19_18-55-12.png

Here the Test Framework and Scriptable Build Pipeline packages have been added as dependency of other packages.

Please note that as mentioned in the first post, a proper cleansing was already applied, but it still caused incomprehensible issues. Hence that thread. The suppression of Localization package has also deleted the Addressables one. Since the former needed the later I figured that deleting the former than the latter would be good but it surprisingly proved unnecessary. A soft nuking later and purging Library again, there doesn’t seem to be lingering references hidden in the project that cause errors, notably in the Editor + Run mode.