Get a 500 over the rest api during deletion of unkown containers

[codemaker219]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

With upgrade to podman 3.0.1 we will get a 500 if we try to delete forcefully a container that does not exists. Before it was a 204 (what also is not the best response code)

Steps to reproduce the issue:

1. Start the rest api podman system service tcp:0.0.0.0:8099 -t0

2. Try to delete a container forcefully that does not exists curl -s -vvv -X DELETE http://127.0.0.1:8099/v1.40.0/libpod/containers/unkown?force=true

Describe the results you received:
A 500 responsecode

Describe the results you expected:
A 404 responsecode

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

Version:      3.0.1
API Version:  3.0.0
Go Version:   go1.14.12
Built:        Tue Mar  2 21:31:11 2021
OS/Arch:      linux/amd64

Output of `podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.19.4
  cgroupManager: systemd
  cgroupVersion: v1
  conmon:
    package: conmon-2.0.26-4.el8.5.2.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.26, commit: 6ce9825c91d32f9890be05932c8e5a39c6a8ae2a'
  cpus: 8
  distribution:
    distribution: '"centos"'
    version: "8"
  eventLogger: journald
  hostname: localhost.localdomain
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 4.18.0-240.15.1.el8_3.x86_64
  linkmode: dynamic
  memFree: 9583484928
  memTotal: 16601899008
  ociRuntime:
    name: crun
    package: crun-0.18-3.el8.5.2.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.18
      commit: 808420efe3dc2b44d6db9f1a3fac8361dde42a95
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  remoteSocket:
    path: /run/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: false
    seccompEnabled: true
    selinuxEnabled: true
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 0
  swapTotal: 0
  uptime: 2h 18m 10.87s (Approximately 0.08 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 17
    paused: 0
    running: 17
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageStore:
    number: 22
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 3.0.0
  Built: 1614717071
  BuiltTime: Tue Mar  2 21:31:11 2021
  GitCommit: ""
  GoVersion: go1.14.12
  OsArch: linux/amd64
  Version: 3.0.1```

**Package info (e.g. output of `rpm -q podman` or `apt list podman`):**

podman-3.0.1-2.el8.3.2.x86_64

**Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?**

Yes

**Additional environment details (AWS, VirtualBox, physical, etc.):**

[mheon]

@rhatdan I"m pretty sure this was your refactor of the Remove endpoint to use common code?

[mheon]

Fixed by #9681