[BUG] Misaligned DataFrame Schemas

[kmaphoenix]

Current Behavior

Currently, there are several areas in SCRAPI that we export and import DataFrames, and their schemas are misaligned.
This causes issues with streamlining a pipeline of events because column renaming or ETLs need to be done.

Examples:
Intents.intent_proto_to_dataframe exports columns = display_name, training_phrase in basic mode.
In advanced mode for the same method, the utterance is now called text.
Mismatch of schema and semantics in the same method.

In DataframeFunctions.bulk_update_intents_from_dataframe, the basic mode expects input columns of display_name and text.
This is misaligned from the above schemas of the generated dataframes in Intents class.

So if your workflow is this:

1. Intents to Dataframe
2. Dataframe to Sheet
3. Sheet to Dataframe

Step 3 will break due to misaligned schema.
We should always be in alignment with "like for like" export/import (i.e. basic and basic should match 100%).
We should also be in alignment semantically across modes (i.e. basic and advanced have different schemas, but the columns that are shared are 100% named identically)

Expected Behavior

All DataFrame schemas within the same Resource type (i.e. Intents, Entity Types, etc.) should be in alignment.

Possible Solution

Centralize the creation and validation of all schema types to a file outside of the class that is using them.
Introduce core/schemas.py or similar to maintain a central schema repository.
Then each respective class can pull their schema and schema validation rules from the central class, ensuring that we have continuity in DataFrame resources.

Steps to Reproduce

Try the following

1. Intents to Dataframe
2. Dataframe to Sheet
3. Sheet to Dataframe (without modifying your sheet. leave it as-is)

[kmaphoenix]

@MRyderOC I found this bug / issue when prepping for my SCRAPI demo today.
More of a minor annoyance than a bug, but I think we should be able to easily enforce this across the entire library.

cc: @Greenford @SeanScripts @cgibson6279
in case y'all want to weigh, help triage, or have any ideas other than what I offered.

[Greenford]

Certainly in favor of a centralized solution for column-naming. I've also run into this problem a few times