Remove `licensed` type from Feature Flags [RUN ALL RSPEC] [RUN AS-IF-FOSS]

What does this MR do?

Contributes to #259611 (closed) Contributes to #271275 (closed)

Links

• The main discussion on why it can be removed #259611 (comment 434476579)
• Clean up issue #273362 (closed)

Feature flags affected by this MR and their states

• jira_issues_integration - production: Not exists https://gitlab.slack.com/archives/C101F3796/p1611829272404600
• jira_vulnerabilities_integration - production: Not exists https://gitlab.slack.com/archives/C101F3796/p1611829353404800
• wip_limits - production: Not exists https://gitlab.slack.com/archives/C101F3796/p1611829408405000
• swimlanes - production: Not exists https://gitlab.slack.com/archives/C101F3796/p1611829456405200
• issue_weights - production: Not exists https://gitlab.slack.com/archives/C101F3796/p1611829506405400
• enforce_pat_expiration - production: Not exists https://gitlab.slack.com/archives/C101F3796/p1611829632406600
• personal_access_token_expiration_policy - production: Not exists https://gitlab.slack.com/archives/C101F3796/p1611829682406800
• multiple_merge_request_assignees - production: Enabled globally https://gitlab.slack.com/archives/C101F3796/p1611829718407200

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability 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
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team