Resolve EE differences in app/views/profiles/keys

What does this MR do?

Resolves EE differences with an OO solution of adding a default method in the base CE class, which is overridden in the EE child class.

This is partially a counter-part for CE merge request but this MR builds on top of that with EE-specific changes

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Performance and testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers

Links

• Closes #10506 (closed)
• Closes #6227 (closed)