[TB] Prepare new release of Theme Builder

[aaronreed708]

Problem/Concern

We have recently put in new changes to our documentation and updated our dependencies. We should push out a new version of Theme Builder with these changes so that any new participants are looking at the new changes. At the highest level, this simply means pushing from dev branch to master. But we need to follow our release process (follow, improve #720). Particularly remember to do container scanning and posting results in /securityscanning.

Questions:

• [x] Current release level of Theme Builder is v1.1.0. What should new version be? v1.2.0?
• [x] Decide on timeframe
• [x] Any pending changes worth waiting for?
• [x] I assume new release of SDK, too? Is it at a good point to push to master?

[PaulaPaul]

@evangk6 - here are my notes (please feel free to add/correct if needed!)

On today's call we decided the new version would be 1.2.0 (no breaking changes, but more than just updating dependencies)

Expecting @aaronreed708 to create the release, and once Keith's changes are in for the SDK we can release.

Please let @PaulaPaul know and she can help amplify the release through FINOS-

[evangk6]

Thanks Paula!

I'll add that specific changes we are waiting on are #501, and the update should therefore in include the SDK as well.

[aaronreed708]

We have an issue that needs to be corrected in our Docker images due to chroma-js issue (#983). We also have some dependency updates that need to be propagated to main. I am proposing that we make this change before #501 is ready so that our latest Docker image doesn't remain broken much longer.