PLATFORM-5905 - Make AttributeError handling more precise

[andrsdt]

PLATFORM-5905

💡 Context

When Pypendency fails to load a module with an AttributeError, it assumes that it was because the DI file didn’t have a load() method. This isn’t always the case. For example, this code:

def load(container_builder: ContainerBuilder):
    container_builder.set_definition(
        Definition('example.A', 'tests.resources.class_a.A')
    )

    x = 42
    x.append(1)

Would raise an exception like this one:

Resource 'test_di_with_generic_attribute_error.py' requires loader method

When the problem is really that the method append doesn't exist in numbers.

📖 Summary

This PR improves the error handling mechanism by raising the unknown AttributeError in case it isn't caused by a missing load function

⚡️Performance Considerations

Negligible. Adds a string check when the module loading fails.

🧪 How should this be manually tested?

• Copy the src/pypendency folder and paste it the src/ folder of a project that uses Pypendency. This will be enough for "patching" it
• Modify any python dependency injection file and add these changes inside the load method:

x = 42
x.append(1)

• Start the project and check that the error raised now is the AttributeError pointing at the append(), instead of mistakenly saying that the load() function is missing

[kb05]

🚀 🎸