Added excludeAction param

[AlexAndBear]

Description

Adding excludeActions parameter to fileActions registerDefaultActions

Motivation and Context

Imagine you write your own file list for a specific app, you want you to use all the default actions, but not the 'Rename' action.
Therefore you needed to define all the actions again in the app. This can now be overcome by passing ['Rename'] as excludeActions parameter.

How Has This Been Tested?

Manual UI Testing

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[JammingBen]

@phil-davis any clue why the js tests are failing ?

As mentioned in the review, I assume it's due to includes(). At least we can give it a try 🙂

[JammingBen]

Nice! Add a changelog, then it's good to go from my side 🚀

[AlexAndBear]

@jvillafanez cool with it?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[jvillafanez]

My only "complain" is that the defaultActions variable seems too big and it makes the function difficult to read. It's a bit easy to lose focus on what the function is doing. Taking into account that we don't plan to add more default actions there, it could be fine since we probably don't want to keep a copy of that variable somewhere else.
Anyway, I'm approving since I don't have better options at the moment.