implement custom templated launch for sso browser option

[meyerjrr]

What changed?

Custom browser launch templates were added in #731. This PR extends on the work done there to include this functionality in adding custom launch templates for the sso browser launch process.

The current logic added will prioritise a custom SSOBrowserLaunchTemplate being set, then CustomSSOBrowserPath and finally with os default open()

Why?

Fixes/provides a builtin workaround for #602

How did you test it?

• Set up custom template for new SSOBrowserLaunchTemplate

[SSOBrowserLaunchTemplate]
  Command = "open -a Safari {{ .URL }}"

Confirmed safari opened correctly when authenticating with SSO.

Potential risks

Is patch release candidate?

Link to relevant docs PRs

[meyerjrr]

I have updated this PR to work more extensively. Specifically I was attempting to use it to solve this issue: #713

I found the adding the following custom browser launch template would not work due to the spaces in "Google Chrome" and the toml reading did not respect the escaping I tried.

[SSOBrowserLaunchTemplate]
  Command = "open -a Google\ Chrome --args --profile-directory=default {{ .URL }}"

I have added a workaround to get this working:

[SSOBrowserLaunchTemplate]
  Command = "\"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\" {{ .URL }} --args \"--profile-directory=Profile 2\" "

Where Granted will now handle anything within quotes as a single argument in the command.

Will need to be added to docs but to find the name of your default profile. Open chrome in your profile of choice and go to chrome://version/ and you should see the profile path:

Profile Path: /Users/<name>/Library/Application Support/Google/Chrome/Profile 2

So "Profile 2" is the profile to set in the above command for --profile-directory