Rename define.NewFixture to define.NewFixtureFromLocalBuild

[AndersonQ]

What does this PR do?

Rename define.NewFixture to define.NewFixtureFromLocalBuild

Why is it important?

There were two NewFixture functions returning the same fixture: testing.NewFixture and define.NewFixture. They basically differ on where the agent package comes from. This is rather confusing and easily lead to mistakes.
testing.NewFixture is the one which actually creates the fixture, whereas define.NewFixture is a wrapper around testing.NewFixture so it'll use the locally built agent artifact. Therefore define.NewFixture was renamed to define.NewFixtureFromLocalBuild, better reflecting what it does.

Checklist

• My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added an entry in ./changelog/fragments using the changelog tool
• [ ] I have added an integration test or an E2E test

Related issues

• N/A

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @AndersonQ? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elastic-sonarqube]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube