Additional documentation for configuring the SGP for initializing phase.

[mikailcolak]

To keep the behavior of the previous version after upgrading the SPG, we have needed to alter the initialization via the described method in README.md within this PR.

And we thought documenting this may help the persons of interest.

[github-actions]

File	Coverage [39.47%]	❌
GranularPermissionsAutoConfiguration.java	39.47%	❌

Total Project Coverage	86.46%	🍏

[iznenad]

I still believe that the library itself should not remove permissions by default. Once removed, and in the case where removal was accidental, the permissions would need to be manually added back to customer roles. This would cause a much bigger impact than some unused permissions sitting in the database. Hence, i'd prefer if we have to configure the library to remove permissions rather than the opposite. In the perfect case the library just doesn't care about this and the app developer has to think about this. I like very much the idea of reporting such unused permissions by logging.

[vladaspasic]

I still believe that the library itself should not remove permissions by default. Once removed, and in the case where removal was accidental, the permissions would need to be manually added back to customer roles. This would cause a much bigger impact than some unused permissions sitting in the database. Hence, i'd prefer if we have to configure the library to remove permissions rather than the opposite. In the perfect case the library just doesn't care about this and the app developer has to think about this. I like very much the idea of reporting such unused permissions by logging.

Why not toggle the behaviour of the using properties? By default it can be turned off