v7.113.0-dev

[joeyzhao2018]

What does this PR do?

Tag current code with a devN version indicating developing for next release.

Motivation

This is needed for APM System testing.

Testing Guidelines

Additional Notes

PEP 440 normalization: The standard requires that development releases use the .devN format (where N is a number, defaulting to 0 if not specified)

Types of Changes

• Bug fix
• New feature
• Breaking change
• Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

• This PR's description is comprehensive
• This PR contains breaking changes that are documented in the description
• This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
• This PR impacts documentation, and it has been updated (or a ticket has been logged)
• This PR's changes are covered by the automated tests
• This PR collects user input/sensitive content into Datadog
• This PR passes the integration tests (ask a Datadog member to run the tests)

[duncanista]

Not sure why we have to make this change on our repo.

If you asked me, the APM System Tests should take care of this by the step they're downloading the repo to build it (I suppose).

This brings two problems:

1. Now, everytime we release, we'd have to raise another PR which removes the .devN from the version.
2. After releasing a new version, we'd then have to raise yet another PR to add back this .devN

I propose we do this in the APM System Tests side.