Removed use of Basic authentication for the sample app.

[santiagoars]

[PR] Removed use of Basic authentication for the sample app.

## Description
The ords-remix-jwt-sample template was originally using Basic authentication when executing requests to the different handlers defined in ORDS. Since using Basic auth is not really a best practice, a ticket was opened to remove it. Instead, the end user endpoints are no longer protected and can be accessed by any user. The end user can only execute read-only actions, so it is fine to have it public. 

Fixes # (issue number)

## Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update

## How Has This Been Tested?
In order to test what type of auth is used, requests were made throughout the application using both the normal end user and an authenticated user. Logs were printed inside the `ORDSFetcher` function to compare the `authCredentials` being used when the user requests the home page.

- [ ] End User

AUTH:  
AUTH:  
AUTH:  
AUTH:  
GET /home 200 - - 2147.232 ms

- [ ] Authenticated User

AUTH:  Bearer <token>
AUTH:  Bearer <token>
AUTH:  Bearer <token>
AUTH:  Bearer <token>
GET /home 200 - - 1829.794 ms

## Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [n/a] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings/errors
- [x] I have added tests that prove my fix is effective or that my feature works
- [n/a] New and existing unit tests pass locally with my changes

[oiramS]

@santiagoars Uppon further inspection of the changes, noticed that the discover functionality is now inaccessible if the user is not logged in, we may need to make those endpoints public as well and update the corresponding documentation section to avoid loss of service.

[santiagoars]

List of things to do before closing the ticket:

• 1. Fix the discover functionality so that it works with an unauthorized user.
• 2. Modify the ORDSFetcher file to only use the credentials if they are != null. If null, then don't pass empty string.
• 3. Update the ORDS Concert App - Securing Services documentation, this includes:
• Protecting our API Endpoints Explain that the concert_app.euser.v1 module is not protected.
• Third Step: Grant permissions to the recently created API. Remove the concert_app_euser privilege from the table.
• 4. In the ORDS Concert App - Defining and Creating the RESTful services add a section to explain that the concert_app.euser.v1 module is public.
• 5. In the auth0Strategy function, remove the concert_app_euser scope.
• 6. In the concert_app.euser.v1.sql module export, remove the concert_app_euser privilege (please export the new module definition and use it to update this document).
• 7. In the concert_sample_app.sql export, remove the concert_app_euser privilege (please export the definition and use it to update this document).
• 8. In the openAPI catalog of the euser module (https://github.com/oracle/create-database-app/blob/main/templates/ords-remix-jwt-sample/ords/openAPI%20Catalog/concert_app.euser.v1.json), update the openAPI catalog with the new definition of the euser module.

[oiramS]

Please implement the requested changes and close the threads that will be implemented in a future PR. Once that is done re-request another review.

[oiramS]

Could you also please:

• Update the whole export of the schema https://github.com/oracle/create-database-app/blob/main/templates/ords-remix-jwt-sample/Database/Modules/CONCERT_SAMPLE_APP.sql so the changes are also reflected there, I think I did this import using SQL Developer, let me double check.
• Bump the euser module version to v2

  create-database-app/templates/ords-remix-jwt-sample/ords/modules/endUserModule.js

  Line 28 in 597e88e

  'euser/v1/',

  , since this is effectively a new version of the API

[santiagoars]

I executed the CONCERT_SAMPLE_APP.sql directly in DB Actions and it executed correctly.

[santiagoars]

List of things to do before closing the ticket:

• 1. Fix the discover functionality so that it works with an unauthorized user.
• 2. Modify the ORDSFetcher file to only use the credentials if they are != null. If null, then don't pass empty string.
• 3. Update the ORDS Concert App - Securing Services documentation, this includes:
• Protecting our API Endpoints Explain that the concert_app.euser.v1 module is not protected.
• Third Step: Grant permissions to the recently created API. Remove the concert_app_euser privilege from the table.
• 4. In the ORDS Concert App - Defining and Creating the RESTful services add a section to explain that the concert_app.euser.v1 module is public.
• 5. In the auth0Strategy function, remove the concert_app_euser scope.
• 6. In the concert_app.euser.v1.sql module export, remove the concert_app_euser privilege (please export the new module definition and use it to update this document).
• 7. In the concert_sample_app.sql export, remove the concert_app_euser privilege (please export the definition and use it to update this document).
• 8. In the openAPI catalog of the euser module (https://github.com/oracle/create-database-app/blob/main/templates/ords-remix-jwt-sample/ords/openAPI%20Catalog/concert_app.euser.v1.json), update the openAPI catalog with the new definition of the euser module.

Just for reference, the unchecked items in this comment will be worked on a different PR.

[oiramS]

Assigning to @dbtools-antcampo so this can be merged.