[Security Solution][Detections] Endpoint Exceptions no longer restrict 'file.path.*' fields in field selector

[kevinlog]

Kibana version:
7.13, 8.0

Elasticsearch version:
7.13, 8.0

Describe the bug:
In the exceptions workflow, when creating an Endpoint Exception, there's no longer a restriction on the file.path field. I can see options for file.path, file.path.caseless, and file.path.text. Before, there was a restriction on creating exceptions to only accept file.path.caseless

Steps to reproduce:

1. Go to the Detections tab and create an Endpoint Exception from an Alert
2. See in the dropdown for field selection that file.path, file.path.caseless, and file.path.text are all available

Expected behavior:
Users should be restricted to selecting file.path.caseless

Screenshots (if relevant):

Any additional context:
I noticed that we used to user this helper which pulls in exceptionable fields based on type: 'endpoint': https://github.com/elastic/kibana/blob/master/x-pack/plugins/security_solution/public/common/components/exceptions/builder/helpers.tsx#L15

I think this is now being used which doesn't use exceptionable fields JSON: https://github.com/elastic/kibana/blob/master/x-pack/plugins/lists/public/exceptions/components/builder/helpers.ts#L165

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[kevinlog]

I'm just basing this off of prior functionality. I know a lot of Detections code is being moved right now, so just let me know if this is still expected!

[dplumlee]

addressed by #95266, was a temp bug during the exceptions lift and shift