Route slug vs Resource Name

[drbyte]

I just installed this plugin by following the readme and found that it didn't auto-register (maybe that's a bug itself, but not the topic at hand in this Issue).
... so I followed the next instruction to extend the base ActivityResource class into my own project.

As long as I named my extended class as ActivityResource, the plugin is correctly accessible at /activities route.
However, if I name my extended class to ActivityLogResource, the route changes to activity-logs, and throws an error Route [filament.admin.resources.activities.view] not defined. when calling \Filament\Resources\Resource::getUrl()

Same error happens when I name my extended class as ActivityResource but set protected static ?string $slug='activity-logs';.

In my present application, I use the term "Activity" to refer to something other than "site activity logs", so would prefer to name it differently.

[alexjustesen]

Just a heads up #60