Fix deprecated-method warnings for "assertEquals"

[pgombar]

Description

Replace assertEquals with assertEqual since the former is deprecated according to pylint.

---

PR information

• The title of the PR is clear and informative.
• There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
• Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes in the description.
• New Unit tests were added for the changes made and Travis.CI is passing.

Quality of Code and Contribution Guidelines

• I have read the contribution guidelines.

[kevinclark19a]

Everything here looks good, but I think you've missed some of the error suppressions. I used this regex on your branch to find them:

# pylint disable=.*(?:deprecated-method|W1505)

Here are the three I found:

/home/kevinclark19a/dev/WALinuxAgent/azurelinuxagent/common/future.py:53
/home/kevinclark19a/dev/WALinuxAgent/azurelinuxagent/common/future.py:66
/home/kevinclark19a/dev/WALinuxAgent/azurelinuxagent/common/version.py:90

I think the issue here was that these use the error code (W1505) instead of the symbol (deprecated-method).

[pgombar]

Everything here looks good, but I think you've missed some of the error suppressions. I used this regex on your branch to find them:

# pylint disable=.*(?:deprecated-method|W1505)

Here are the three I found:

/home/kevinclark19a/dev/WALinuxAgent/azurelinuxagent/common/future.py:53
/home/kevinclark19a/dev/WALinuxAgent/azurelinuxagent/common/future.py:66
/home/kevinclark19a/dev/WALinuxAgent/azurelinuxagent/common/version.py:90

I think the issue here was that these use the error code (W1505) instead of the symbol (deprecated-method).

Correct, but if you take a closer look at what these are, you will find that the suppression should stay there since we are not changing that code.

[kevinclark19a]

Awesome! Yep, that checks out.