Refactoring SQL joblog view

[buzzia2001]

Changes

With this PR, the view for WRKJOB has been updated to use the one from the FS extension.

How to test this PR

1. Connect to a system and hover over the name of the database connection profile

2. A new tab containing WRKJOB will open

Checklist

• have tested my change
• have created one or more test cases
• updated relevant documentation
• Remove any/all console.logs I added
• have added myself to the contributors' list in CONTRIBUTING.md

[sebjulliand]

@buzzia2001 I like the idea, but there are two suggestions I would make:

• There is the SQL job from the core that could benefit from having a joblog viewer
  
• In this case, the joblog webview should be moved to the core, so there is no circular dependency between Core and FS

What do you think ?

[NicolasSchindler]

@sebjulliand @buzzia2001 and i are already on that :) I prepare a PR later for the Core. Also to include the JDBC configuration of the Mapepire job

[sebjulliand]

@sebjulliand @buzzia2001 and i are already on that :) I prepare a PR later for the Core. Also to include the JDBC configuration of the Mapepire job

Ok, cool!
Be careful about putting the JDBC options in the Core. The core's job is not meant to be overly configurable since it's used for the core's processes. It would be a shame if users could break it by misconfiguring it.

[buzzia2001]

Ciao @sebjulliand @NicolasSchindler ,

I'll I'll move the WRKJOB view into the core extension, but I also have to move the frontend, so it'll take a little while.

[sebjulliand]

@buzzia2001 sure, no rush 😄

[buzzia2001]

@SanjulaGanepola and @sebjulliand

I've updated this PR to use the new joblog command that's included in the core. I've also added the job ID to the tooltip; you can copy it just like on ACS if you want.

[buzzia2001]

@SanjulaGanepola updated as requested

[SanjulaGanepola]

Works great!

Before we do a release, we should make sure to do a bump of the Code4i types once that is released to get rid of: