Remove console.log from code and enforce ESLint rule

[saschaszott]

Description

Currently, there are three occurrences of console.log in the codebase that should be removed:

dspace-angular/src/app/shared/access-control-form-container/access-control-form-container.component.ts

Line 101 in 073cd07

console.log({

dspace-angular/src/app/shared/access-control-form-container/access-control-form-container.component.ts

Line 141 in 073cd07

console.log('success', res);

dspace-angular/src/app/shared/access-control-form-container/bulk-access-control.service.ts

Line 62 in 073cd07

console.log('execute', { uuids, file });

Additionally, to prevent console.log from being introduced in the future, an ESLint rule "no-console": "error" should be added to enforce this convention.

[tdonohue]

@saschaszott : I agree with this entirely. If you find time to create a PR, I'd gladly review it. Plus, the ESlint rule would help immensely in ensuring we don't accidentally add more console.log statements in the future.

[alanorth]

I was surprised to find that we already use the ESLint "no-console" rule, but log is allowed:

https://github.com/DSpace/dspace-angular/blob/main/.eslintrc.json#L70-L74

There are many more instances of console.log() that are for debugging purposes during build etc, so it seems we will need to update this ESLint configuration with some exceptions or change those to console.warn() or info...