Add normalization to destination definition and actor definition table

[andriikorotkov]

What

updated StandardDestinationDefinition.yaml, added normalization and tags to the destination_definition.yaml and added information about normalization and DBT to the ACTOR_DEFINITION table

How

I added the fields we need for DBT and Normalization in StandardDestinationDefinition.yaml. Also, I expanded the ACTOR_DEFINITION table a bit, in order to store the values of destinations normalization and DBT where needed (the new fields can be null, since the ACTOR_DEFINITION table also stores information about sources and destinations that do not support normalization). Since the path by which the migration file was created has already been added to gradle, during the build of the platform, the new migration will be performed, and the fields will be added to the table.

Recommended reading order

1. StandardDestinationDefinition.yaml
2. V0_40_15_001__AddActorDefinitionNormalizationAndDbtColumns.java
3. ConfigWriter.java

🚨 User Impact 🚨

Currently, it does not add any impact to the platform. But in the future, we will use values for normalization and DBT fields from the definition file.

[andriikorotkov]

@evantahler @tuliren @pedroslopez, I plan to completely close the first step from the document "Decouple Normalization from Platform" with this pull request. In my opinion, this is all that should be done in the first step, but I could be wrong and miss something. If I've done something wrong, please let me know and I'll fix it.

[alafanechere]

Hey @andriikorotkov could you please create an issue related to this PR?
If I understand correctly you try to achieve these steps from the tech-spec right?

Step 1: update StandardDestinationDefinition.yaml
Add the new fields to the definition
Regenerate the model class locally
Copy the information from the spec file to the definition file

As I'm not very familiar with the ConfigWriter and the migrations would you mind adding more details to the How section? I'd also appreciate the User Impact to be filled to share how this will be deployed and could be rolled back.
Feel free to change the status to Ready for review when it's ready :)

[andriikorotkov]

@alafanechere, yes, you are right, I am trying to do this exact part from our documentation (1 step). Also, I have already created subtasks for each of the steps. Also, I seem to have added this pull request to the right task.

Link to the issue for the first step - 18230

Link to the issue that I turned into a small epic - 17915

[alafanechere]

Thanks for providing more description.
I think you need to format your branch to follow our linting rules:
./gradlew format. (Please install pre-commit to avoid these problem in the future: pre-commit intall)

Moreover the platform build is failing with this error:
org.opentest4j.AssertionFailedError: expected: <0.40.12.001> but was: <0.40.15.001>

How did you pick the version the migration will be run for?

[evantahler]

Adding @colesnodgrass and @jdpgrailsdev from the platform team for review as well