Style updates

[pngwn]

This PR introduces some style changes to ensure that user can't completely break theirs app with the options that get passed in. There are also a few changes to Simplify how certain things are handled. Other changes are simply hooking

• Colors have been removed for now, I think colors should be handled via whatever theming mechanism we choose. In the case that users want a different color for a certain gradio block (so it stands out for example), I think we should allow Box to have a few variants, maybe default, info, warning and error each with their own background style but that works well for both luight and dark mode. The colors for these 'types' would be customisable with the themeing system (that doesn't yet exist).
• color_map still exists where it is used and is unchanged, i have moved this kwarg from the component to the style method. The rationale here is that anything that only affects the visuals should be a style kwarg. show_label is a bit of an anomaly here but it feels kindof logical. We could move it as well though.
• container is a style kwarg now, same logic as above.
• container_bg_color has been removed. Instead of allowing people to modify the container in this way (and end up with lots of container_* styles), we should encourage users to set container=False and use gr.Box() which they can pass some styles too.
• I'm really not sure where it makes sense to disable the container. In some cases it is fine but all of the upload components need the container for the dotted border + drop highlight functionality. Disabling that will break the ui pretty badly.
• I'm a bit confused about margin, only a few components actually have margins, most of the time the margins are actually paddings and i think we can remove them when the container=False. But that means we need a way to add them back, I'm not sure what that should be.
• rounded also gets a little confusing. I tried to make it so that the round is relating to whatever the main part of the component is but it is a little confusing. On form inputs (Textbox, Number, Checkbox, etc) it relates tot he input itself, this looks fine on most but terrible on checkbox + radio. Onfile upload components, this actually refers to the containing box which makes sense (ish) because that is the component but is also slightly inconsistent with the fporm inputs. For table I'm not sure if this will break anything.

note: there will probably be loads of conflicts when some of the current PRs go in. This PR is unfinished, I've been back and forth on a number of options and wanted to get other people's thoughts before I continued. There isn't much left to do in terms of hooking the last few styles up in the frontend

Tech stuff

I also refactored the way in which styles are applied in the frontend but that is an implementation detail. Happy to go through it @aliabid94. Some inert code still needs removing.

[pngwn]

cc @abidlabs @aliabid94 @gary149

[abidlabs]

This approach generally looks good to me @pngwn. I skimmed through the components and it looks like we're providing users with a good set of initial styling parameters to start with. We'll need to add more over time as users request them, but they should already be able to go pretty far with this.

I'll let @aliabid94 and @gary149 speak more on the actual frontend changes. With regards to the backend, lets make sure to throw deprecation warnings when we're moving parameters (I created an example -- can create the others once everything else is finalized)

[pngwn]

Added deprecation warnings and reimplemented the color_maps where appropriate. Resolved conflicts.

[aliabid94]

Interesting, I think this makes sense for the most part. the whole variant as "info", "warning", etc. system reminds me of bootstrap which doesn't allow that much flexibility, but I guess theming is a different discussion. I'm thinking if there are other style properties we should add - rounded and container stuff is pretty limited customization.

[pngwn]

@aliabid94 The focus here is essentially just for things people might need to modify to get different layouts. I think style customisations across the board should be handled via themes (indluing scoping 'themes' to invidual component instances or providing theme value overrides for individual component instances). This why i removed the colors specifically (mainly because dark mode makes defining colours really difficult).

I actually went through and looked at every component in detail and the margin setting basically didn't do anything and really couldn't, nothing has margins for the most part. I made sure to strip any margin or padding when container=False, as well as handling the case when container=False but show_label=True. I removed border options from most of the input components because it completely breaks the UX when dragging files.

I think it is better to strip things down for now because it is far easier to add stuff than to remove. The options we had (many of which didn't make sense or didn't do anything) are a good example of what will happen if we just add things on a case by case basis. We need to look at styling/ theming holistically and not just add things piecemeal, or i think it will get out of hand and give unexpected results.

[pngwn]

Merging before there are any more conflicts.