server route for getpercentile method

[karishma-gangwani]

Description

I tested it with the SJ life dataset by running logistic regression. and all tests passed on my local. There are some types in there that need to be defined better. I think I will get to that afterward after discussing it with Colleen and Edgar. Let me know if this looks good.

Checklist

Check each task that has been performed or verified to be not applicable.

• Tests: added and/or passed unit and integration tests, or N/A
• Todos: commented or documented, or N/A
• Notable Changes: updated release.txt, prefixed a commit message with "fix:" or "feat:", added to an internal tracking document, or N/A

[xzhou82]

looks good and all seem to work

[xzhou82]

can fix this so all server unit tests will pass?

/home/runner/work/proteinpaint/proteinpaint/server/routes/burden.ts
97:35 error Don't use {} as a type. {} actually means "any non-nullish value".

• If you want a type meaning "any object", you probably want object instead.
• If you want a type meaning "any value", you probably want unknown instead.
• If you want a type meaning "empty object", you probably want Record<string, never> instead.
• If you really want a type meaning "any non-nullish value", you probably want NonNullable<unknown> instead @typescript-eslint/ban-types

[karishma-gangwani]

can fix this so all server unit tests will pass?

/home/runner/work/proteinpaint/proteinpaint/server/routes/burden.ts
97:35 error Don't use {} as a type. {} actually means "any non-nullish value".

• If you want a type meaning "any object", you probably want object instead.
• If you want a type meaning "any value", you probably want unknown instead.
• If you want a type meaning "empty object", you probably want Record<string, never> instead.
• If you really want a type meaning "any non-nullish value", you probably want NonNullable<unknown> instead @typescript-eslint/ban-types

thanks for pointing out. I just pushed a fix.