Add a path field to support Pathauto

We should be adding the field on the entity itself.

Here's a patch for adding a path base field to the Profile entity itself.

This will need a bit more thought, because our default use case doesn't require path aliases, and showing such a field by default to existing users (such as the ones using Commerce) would be confusing. So we'd at least need to make sure that the path field is hidden by default.

I was having a gander at this as we want to have path aliases for one of our profile types. It looks like Pathauto can add a 'path' field definition to any entity type that doesn't currently have one - if you go to "/admin/config/search/path/settings" and switch it on for "Profile", then you can configure patterns for profile entities this way and it will appear in the form display as expected.

If paths were to be a default in this module, presumably tests and the .info file would need the "Path" module as a dependency, and field definitions would need to be added in an update hook as well as predefined in the entity? Happy to supply a patch and pop the URL alias in the hidden region, but like @bojanz says, I'm not sure all users would need this. :)

I have re-rolled the patch from comment #4.

I have confirmed that #9 is correct. There is no need for a patch. Just go to /admin/config/search/path/settings and enable Pathauto for Profile.

Thanks, littlepixiez!

#9 worked for me, thanks!