Move redesign CSS files to new subdirectory and retain current CSS for legacy support

[autumnfound]

In discussions with @chrisguindon, we discussed that we need to maintain the legacy CSS as is to support external sites such as jakartablogs.ee and start.jakarta.ee. To do this, we will want to move the new CSS to a subdirectory and point the main Jakarta site to this moved version, and retain the current CSS as is for long term support while the downstream sites are migrated to the new look and feel.

For this, we will want to name the redesign to give it a stable name that won't collide with future versions. In the main EF styles, we use space related terminology to determine these styles. I think the strongest option we have here as a nod to the name Jakarta and pick names of other large cities on the Java island. I'm thinking "surakarta" might be a good city name to use.

[autumnfound]

@shabnammayel @excentrickristy any thoughts on the above "theme" name? If you'd like, we can also avoid naming and use something like wider generic v1, v2, and so forth. This is just for internal communication and would only be referenced on the site when importing the styles and scripts for the theme.

[shabnammayel]

@ivargrimstad and @TanjaObradovic WDYT? should we go by version (v1 & v2) for now. We need to decide asap to launch on Monday as planned

[autumnfound]

For now, we have v1/v2 in use to ensure we can go live. Once we have a final decision on a branding name, we can easily update it! We've done testing to ensure that the downstream services like start.jakarta.ee render correctly, which is the biggest thing we needed for the launch of the redesign.