Use Integrations Path when creating new classes

[JonPurvis]

Fixes #47

When working on #46, I added the ability to specify an integrations_path within the Saloon config file, so that if an application was using a different architecture, such as DDD, the saloon:list command would continue to work, providing that the config value was set correctly.

This PR goes one step further with that config value, in that if it's set, it will create classes in that path. Let's say we have an application using the DDD approach. Instead of our integrations living in the default location of app/Http/Integrations, we have them in app/Domain and have updated the saloon.integrations_path so it's correct, when we run php artisan saloon:request and fill in all the prompts, you'll see:

Note the path in the confirmation message

If we wanted to segment them further, perhaps we integrate with multiple Payment APIs, we could set Payment/Stripe as the Integration name, and that will give us the following:

If the saloon.integrations_path config isn't set in the application, then it will fallback to use the default location of app/Http/Integrations:

I can also confirm that saloon:list will still work:

I'm pretty happy with the little amount of code this took to achieve. This update has definitely been a long time coming, that's for sure! As always, I'm happy for any feedback!

[JonPurvis]

@Sammyjo20 As promised! 😄

Would you be able to take this for a test drive?

[Sammyjo20]

Hey @JonPurvis sorry for the slow reply on this one! Thank you so much for adding this functionality - I will give this a test drive this weekend.

[JonPurvis]

Hey @Sammyjo20 not a problem, you're a busy guy! 😄 Let me know if you spot anything you want changing and I'll get right on it!

[Sammyjo20]

This works really well amazing work as always @JonPurvis - Thank you