I have checked the following:

• I use the newest version of bruno.
• I've searched existing issues and found nothing related to my issue.

Describe the bug

When executing the request, bruno goes through several stages of configuration, among them: execution o pre-request script, post-request script, and run of 'configureRequest` method. The current execution order is:

• execute pre-request scripts
• configure request (interpolate vars, sets proxy, auth headers. cookies)
• execute request
• execute post-request

I wonder if it would make more sense to execute the steps in this order:

• configure request
• execute-pre-request script
• execute request
• execute post-request script

This way any logic built into bruno may be overwritten by user's script and on top of that, user's script execute on request that is closer to what is actually being sent (e.g. with variables resolved, headers set).

For example, the below bru file logs this to console:

Before
{{api_url}}
{"Content-Type":"application/json"}

After
https://localhost:8083
{"Content-Type":"application/json","Authorization":"Basic dXNlcjpwYXNzd29yZA=="}

while I would expect the output Before and After to be the same.

.bru file to reproduce the bug

meta {
name: example
type: http
}

post {
url: {{api_url}}
body: text
auth: basic
}

headers {
Content-Type: application/json
}

auth:basic {
username: user
password: password
}

script:pre-request {
console.log('Before');
console.log(req.url);
console.log(JSON.stringify(req.getHeaders()));
}

script:post-response {
console.log('After');
console.log(req.url);
console.log(JSON.stringify(req.getHeaders()));
}

Screenshots/Live demo link

N/A