Remove s3_access As Required From update_account_s3_access

[shirady]

Explain the changes

1. Remove s3_access as required from update_account_s3_access. The use of s3_access was historical: before the UI was deprecated we had two types of accounts:
   (1) account access S3
   (2) account UI - account UI was for using the UI and it didn't have s3_access.
   Today all accounts have s3_access.

Issues: Fixed #7204

1. In the opened issue this is a fix to the comment.

Testing Instructions:

1. none

• Doc added/updated
• Tests added

[liranmauda]

LGTM

rethinking...

[liranmauda]

Based on the explanation, It all accounts should have s3_access then:

1. In the create_account we should remove the if:

   noobaa-core/src/server/system_services/account_server.js

   Line 85 in 50a6761

   if (req.rpc_params.s3_access) {

2. Same goes for the update_account_s3_access:

   noobaa-core/src/server/system_services/account_server.js

   Line 330 in 50a6761

   if (req.rpc_params.s3_access) {

   and:

   noobaa-core/src/server/system_services/account_server.js

   Line 384 in 50a6761

   if (req.rpc_params.s3_access) {

   and the else of those if should be removed.
3. Same goes for the validate_create_account_params:

   noobaa-core/src/server/system_services/account_server.js

   Line 1294 in 50a6761

   if (req.rpc_params.s3_access) {

Another point is that if we don't need it, we should probably remove the require form create_account and in the account_api.
Moreover, we should probably remove it all completely from the api, create an upgrade script, and fix the Operator calls for those.

[nimrod-becker]

I agree with Liran's comment

[shirady]

@liranmauda, thank you as discussed with @dannyzaken I'll close this PR for now.