Prompt Users to Change Git Repository Branch Settings when Git Project Integration Fails

Currently, if a user tries to connect a git repository through the Default Git Integration Project (or similar) and the git project integration fails because of settings on the git side (e.g., git repository branch rules, but possibly other settings too), the user must manually go to the git repository via the git tooling to change the settings.  This RFE is to request that instead, the backend captures which permissions or other settings were not the right setting from the response it gets from the git server, and prompts the user to attempt to change those settings using the user's token and associated permissions to thereby re-attempt the connection with a preceding call to the git server's API with the necessary changes and the user's token (e.g., https://docs.gitlab.com/api/project_push_rules/).  If the user has the correct permissions on the git repository, the settings would then be adjusted successfully via the api call and the watsonx.ai git connection default git integration project created successfully.  If the user did NOT have the correct permissions on the git repository, the api call would get back an error, and it would report to the user that it needs to contact a git repository user with sufficient permissions to make the necessary changes.

In summary, the flow would be:

-Start attempt to create Default Git Integration project 
-> Success -> End
-> Fail -> Capture failure cause -> Prompt user if they want to attempt to change the git repo and/or branch's settings that caused the failure and retry the connection -> No-> End
-> Yes -> Use git API (depending on type of git, e.g., gitlab: https://docs.gitlab.com/api/project_push_rules/), or GitHub: https://docs.github.com/en/rest/repos/rules) and user token to attempt to change settings that failed -> Success -> Re-attempt connection to project -> Success -> End
-> Fail (re-attempt connection to project) -> Report error to user from logs -> End
-> Fail (use git API & user token to attempt to change git settings that failed) -> Report to user that settings could not be changed on the git server and inform the user to request the help of a git admin or suitable user with appropriate permissions to change the settings for them and then have them manually re-attempt the connection -> End.