[BUG] OpenShift provider should not use DeploymentConfigs (anymore)

[jacksgt]

Expected Behavior

Kompose should use regular Kubernetes Deployments also with --provider=openshift.

Actual Behavior

When invoking kompose convert --provider=openshift, kompose currently creates DeploymentConfig objects for each docker compose service.
However, as of Openshift 4.14 DeploymentConfigs are deprecated.
The Openshift web console shows the following warning:

The oc CLI shows this warning:

$ oc get deploymentconfig 
Warning: apps.openshift.io/v1 DeploymentConfig is deprecated in v4.14+, unavailable in v4.10000+

Steps To Reproduce

kompose convert -f docker-compose.yml --provider=openshift

Kompose Version

1.32.0 (HEAD)

Docker-Compose file

version: '3.2'

services:
  changedetection:
    image: ghcr.io/dgtlmoon/changedetection.io
    container_name: changedetection
    volumes:
      - changedetection-data:/datastore
    environment:
      - LOGGER_LEVEL=INFO
      - PLAYWRIGHT_DRIVER_URL=ws://playwright-chrome:3000
      - HIDE_REFERER=true
    ports:
     - 5000
    restart: unless-stopped
  playwright-chrome:
    image: dgtlmoon/sockpuppetbrowser:latest
    restart: unless-stopped
    environment:
      - SCREEN_WIDTH=1920
      - SCREEN_HEIGHT=1024
      - SCREEN_DEPTH=16
      - MAX_CONCURRENT_CHROME_PROCESSES=2
    ports:
      - 3000
volumes:
  changedetection-data:

Anything else?

https://docs.openshift.com/container-platform/4.15/applications/deployments/what-deployments-are.html

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten