MFTF deprecation notice attributes

[okolesnyk]

Description

Fixed Issues (if relevant)

1. magento/magento2-functional-testing-framework#<issue_number>: Issue title
2. ...

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/verification tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)
• Changes to Framework doesn't have backward incompatible changes for tests or have related Pull Request with fixes to tests

[KevinBKozan]

Small changes requested around constants, logic seems good otherwise.

[coveralls]

Coverage decreased (-1.5%) to 51.926% when pulling 3e86d4f on DeprecatedAttr into e344c6f on MFTF-2.5.5-RC.

[coveralls]

Coverage increased (+0.6%) to 52.497% when pulling a457211 on DeprecatedAttr into 53b055d on develop.

[KevinBKozan]

@okolesnyk Feature is still printing out all deprecated entities on generation; we need to either:

• Suppress printing selectively for our new deprecation notices (done by changing function in MftfLoggingUtil)
• Detect existance of deprecated entities once and only print out a single Deprecated entities detected in MFTF Test files, please check <log file>. This is trickier, would need to keep track of if we've thrown that error at all.

Option one is easier, and works to reduce noise. I think that once we implement this, the deprecated warning will literally always be up once it starts being used, so I actually think we can supress all deprecated test file warnings.

[KevinBKozan]

Missed on first review, should be SectionObject::class I believe.

[KevinBKozan]

LGTM, verification tests look thorough, not concerned about manual test requirements.

The base branch was changed.