fix: Change associations controller path to avoid naming collisions

[aburgel]

Description

Fixes #3525

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

Manual review steps

1. Use repo app from has_many field named actions causes exception #3525 with this branch to show that exception no longer occurs.

Manual reviewer: please leave a comment with output from the test if that's the case.

[codeclimate]

Code Climate has analyzed commit 06aeecb and detected 0 issues on this pull request.

View more on Code Climate.

[Paul-Bob]

Thanks for looking into this, @aburgel. Since the issue that originated this has a simple workaround, I'm closing this PR, and we'll hold off on this refactor for now. We might revisit it in the future.

[aburgel]

@Paul-Bob No worries. Thanks for helping with the workaround.

My team is just starting out with Avo (and paying for Pro) and we generally like to contribute fixes if we can. So it would be helpful to know the best way to help with PRs. Is your concern with this PR more about backward compatibility? Or is it something else?

[Paul-Bob]

My team is just starting out with Avo (and paying for Pro) and we generally like to contribute fixes if we can.

That's awesome! We truly value and appreciate contributions from the community.

So it would be helpful to know the best way to help with PRs.

Normally we discuss the proposed approach and overall direction on the issue thread before diving into the work. However we're absolutely open to direct PRs for more straightforward fixes.

Is your concern with this PR more about backward compatibility?

Thank you for asking! Yes, backward compatibility is one of my primary concerns here. This change would introduce a breaking change for users who currently rely on direct links to certain association pages.

Another consideration is that while this addresses your edge case, the Action model and other cases mentioned in the issue still cannot be created due to conflicts with internal controllers.

There is some work to do around routing and we might get back to this PR