Autogenerate source_type_id when running ddev create

[nmuesch]

What does this PR do?

Adds an auto-generation of "source_type_id" and put it in the manifest.json file during ddev create.

Motivation

This is a field that already exists for all current integrations and followup work will backport the current IDs into the existing manifests.

Otherwise, the rationale can be found here - https://datadoghq.atlassian.net/wiki/spaces/MKT/pages/3306327909/2023-11-27+APW+Integration+Source+Type+ID+Generation

Additional Notes

I was able to test this by running ddev -x create test_integration. Then the resulting test_integration/manifest.json contained the following:

...
  "assets": {
    "integration": {
      "source_type_id": 4526851,
      "source_type_name": "test_integration",
      "configuration": {
        "spec": "assets/configuration/spec.yaml"
      },
...

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Changelog entries must be created for modifications to shipped code
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (110cec7) 90.54% compared to head (3da69db) 90.64%.
Report is 53 commits behind head on master.

Additional details and impacted files

Flag	Coverage Δ
activemq	?
cassandra	?
confluent_platform	?
datadog_checks_dev	82.55% <100.00%> (+0.03%)	⬆️
hive	?
hivemq	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
presto	?
solr	?
tomcat	?
weblogic	?

Flags with carried forward coverage won't be shown. Click here to find out more.

[github-actions]

Test Results

  4 files    4 suites   3m 44s ⏱️
430 tests 430 ✅  0 💤 0 ❌
960 runs  927 ✅ 33 💤 0 ❌

Results for commit 3da69db.

[FlorentClarret]

🥇