Add the ability to exclude selectors from scanner

[abdulahmad307]

There may be situations where there are embedded iframes, 3rd party, or user generated content that should not be scanned. AxeBuilder has the ability to exclude selectors from a scan. We can add this ability and exclude selectors before axe builder analyzes the page.

This will likely require a new input that takes a list of selectors to exclude from the scan.

• Add new input
• Update documentation (md) files
• Update action.yml files
• Add axeBuilder.exclude before running axeBuilder.analyze

We probably want to specify an exclude list per url (as opposed to a global exclude list). We can also have a special 'all' config that applies (merges) that specific config to (with) all urls.

Closing comment from the first PR that copilot started working on.

Actually, I don't think this is the right approach. It would make more sense if each page/url had its own exclude list. We might want to introduce a new urlConfig input that takes a list of objects with the url as a field, and any other configuration options (as opposed to the current flat list of urls). We can keep the old flat url list as an input too for those who don't need the extra configurability