Description of problem:
Setting the parameter 'content_access_mode: org_environment' when manifest object is created for the first time, sets the Simple Content Access attribute correctly.
However, when the 'content_access_mode' parameter is changed, the manifest object is not modified accordingly.

Version-Release number of selected component (if applicable):

How reproducible:
100% reproducible.

Steps to Reproduce:
1. playbook1 for creating a manifest with SCA disabled and then updating it to enable SCA:

~~~

• name: Creating manifest with simple_content_access disabled
  redhat.satellite.redhat_manifest:
  name: "case_03807997_test"
  content_access_mode: "entitlement"
  username: "{{ rh_cdn_username }}"
  password: "{{ rh_cdn_password }}"
  register: manifest

• name: Update the same manifest with simple_content_access enabled
  redhat.satellite.redhat_manifest:
  uuid: "{{ manifest.uuid }}"
  content_access_mode: "org_environment"
  username: "{{ rh_cdn_username }}"
  password: "{{ rh_cdn_password }}"
  ~~~

Result: Manifest is created on the portal with SCA is disabled even using "content_access_mode: "org_environment"

2. Playbook2 for creating manifest with SCA enabled:

~~~
tasks:

• name: Creating manifest with simple_content_access disabled
  redhat.satellite.redhat_manifest:
  name: "case_997_test2"
  content_access_mode: "org_environment"
  username: "{{ rh_cdn_username }}"
  password: "{{ rh_cdn_password }}"
  register: manifest
  ~~~

Result: Manifest created on portal with SCA enabled.

Actual results:
1. Result: Manifest is created on the portal with SCA is disabled even using "content_access_mode: "org_environment"

2. Result: Manifest created on portal with SCA enabled.

If we enable SCA while creating the manifest it works but if we try to update the existing manifest and enable SCA it does not.

Expected results:
When modifying the existing manifest to enable SCA using "content_access_mode: "org_environment" should enable SCA

Additional info: