Add ability to store SAML Service Providers in database

[JamesMowatt]

This PR adds the functionality allowing you to declare service providers within the database rather than a fixed config file.

To use the database instead, set the samlidp.sp to be \CodeGreenCreative\SamlIdp\Models\SamlServiceProvider::class instead of the config array.

[JamesMowatt]

@upwebdesign do you feel this is inline with the package? It's not ready to merge, but want to check you would be happy with this continuing?

[upwebdesign]

@JamesMowatt, I love this idea. I have never liked defining the service providers in the .env file. It's messy and error-prone. Please continue if you have the time. I am currently pressed for time, so I appreciate your contribution.

[JamesMowatt]

@upwebdesign I will continue down this route, will test and tag you when it's ready. Thanks

[JamesMowatt]

@upwebdesign this is ready for review, I have tested it on my local SAML workbench.

[NeilInnes]

Looks great! 😄

[upwebdesign]

Other than the table name, I think this looks good! Let me know your thoughts on renaming the table in the database.

[upwebdesign]

We should prefix the package name with the table name.

laravel_samlidp_service_providers

This naming convention will clarify what the table is for and reduce the likelihood of a collision.

[JamesMowatt]

Absolutely happy with that

[JamesMowatt]

@upwebdesign that is ready to look at again.

[JamesMowatt]

@upwebdesign this is ready for review, hope everything is sorted.

[upwebdesign]

@JamesMowatt, it appears there is a compatibility issue with a method in the migration. publishesMigrations is a Laravel 11 function, but the package supports version 7+. Can you look into this?

[upwebdesign]

It appears this code is the fix. The path may need to be updated.

$this->publishes([
    __DIR__ . '/../database/migrations' => database_path('migrations'),
], 'migrations');