`eslint-plugin-prefer-let`: Forbid to use `const` for non-primitive values

[vanyauhalin]

Hi, thank you for the plugin. Can you please extend its functionality to forbid using const for non-primitive values? The idea is simple, I think the const keyword for evrething except primitive values is missliding, because you can in fact modify it.

const o = {}
o.value = "hello"

const a = []
a.push("gotch you")

Constants

const c0 = ""
const c1 = 0
const c2 = 0n
const c3 = false
const c4 = undefined
const c5 = Symbol("")
const c6 = null

Variables

let v0 = {}
let v1 = []
// etc

References

https://developer.mozilla.org/en-US/docs/Glossary/Primitive

[cowboyd]

I am willing to accept a PR for this if it is as an option that is disabled by default. The reason is that the rule is not designed to be a strict arbiter of what is actually constant and what is not in terms of references and values. It is to encourage code to declare the intent of a value: Is it axiomatic (const) or is just an intermediate value in a computation (let)

For example, take this statement:

const o = Object.freeze({});

This is constant both in terms of being axiomatic, but also in terms of being closed to modification, so it should be allowed by the reasoning above.

I would definitely accept a well-tested PR that included this as an option, so going to close the issue.