Reverting the change to the Hit pydantic modelling.

[THOR300]

Description

Move the concept fields back to the base Hit object.

Proposed version

Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.

• Skip auto-tagging
• Patch
• Minor version
• Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.

Notes:

• If none of these options are selected, auto-tagging will fail (integrated soon)
• Where multiple options are selected, the most senior option ticked will be
  used -- e.g. Major > Minor > Patch
• If you are selecting the version in the list above using the textbox, make
  sure your selected option is marked [x] with no spaces in between the
  brackets and the x

Type of change

Please select the option(s) below that are most relevant:

• Bug fix
• New feature
• Breaking change

How Has This Been Tested?

Unit tests.

[linear]

PLA-459 Revert pydantic changes to the sdk around Concept field movement

[THOR300]

@jamesgorrie do you have any ideas for a unit test to avoid this happening again (backend or sdk)?