feature/DEB-6741-Slickgrid-Changes

@sergiopereiraTT and @kzhdev  Please review.  Thank you.  A new PR will come soon with NTW less files changes.

The performance issue is caused by the createCssRules function, which gets called at the end of grid initialization.  Chrome Timeline shows that it causes 2 seconds delay in opening a new AuditTrail after having opened 10 of them.  This function creates a new <style> and inserts it into the <head>.  This causes the whole page layout to be recalculated.  The more elements there are in the workspace, the more expensive this layout becomes.  We tried to move the <style> element into each slickgrid's <div>, but that did not work, even with scoped style.  

The solution we have now is to move all the style rules into each grid element, and do away with the <style>.  Some of the style rules, such as slick-column-header height/left, slick-cell height and slick-row height can not be changed after the grid is rendered, so they can be easily moved into the corresponding <div> when the html text is generated.  One caveat is that, before, the styles in css file (such as working order cell height) would override the rules in the <style> inserted into the map, while now the hardcoded style would override the ones in the css file.  So we need to change some of the css files to use !important for those to take effect.  The left and right style of each cell takes more effort to make them right, because user can resize column and widgets to affect them after the grid has been rendered.  So anywhere the left and right rules are needed before, we now generate dynamically on the fly.

We tested all the widgets and did not see any difference in the looks with this new change.  Resizing columns and widgets also behave as before.  The change also makes other aspects of the workspace behave faster than before, when there are many grid widgets opened, such as resizing columns, and zooming MDT.